Database
CypherGuard: Database-Grounded Correction for Reliable Text-to-Cypher
arXiv cs.DB0 views
arXiv:2610.41755v1 Announce Type: new Abstract: Text-to-Cypher translates natural-language questions into Cypher queries over property graphs. Graph database systems increasingly adopt this translation as a native query interface. Large language models generate fluent Cypher but stay unreliable. On Cypher-Bench a small model answers only 31.4% of questions correctly, and even a strong model plateaus at 71.76%. The dominant failure modes are structural rather than linguistic. For example, a generated query may parse correctly and follow the schema, yet still return zero rows because it traverses a relationship against the stored graph direction. To address this issue, we present CypherGuard, a training-free framework that detects and corrects these structural faults. Our approach uses two core components: a graph-native error taxonomy to guide repair, and a mined rule library to guide query generation. At inference time, CypherGuard first rewrites schema-detectable faults, then re-executes each draft and repairs it only when the query errors or returns nothing. On CypherBench test questions, across seven graphs, CypherGuard reaches 88.50% overall execution accuracy, +25.08% over the same-backbone zero-shot floor, surpassing an RL-fine-tuned 7B specialist and the strongest training-based system that we compare against.
Source:https://arxiv.org/abs/2610.41755PreviousSupervised and LLM-Augmented Cardinality Estimation for Similarity Queries on Knowledge GraphsNextMerging and Evolution of Data Bases: A Many-Logic Approach
Related posts
Introducing the joint reference architecture for enterprise-grade Redis on VMware Cloud Foundation 9.1
0Redis Blog
Why Enterprise AI Needs Less Guesswork and More Structure
0HackerNoon
Treat Staff Dashboards as Financial Interfaces
0dev.to
Before You Say Yes to an OPT Job Offer: Five Red Flags to Check
0dev.to Security
What five clouds' own docs tell an AI agent about where to keep app data
0dev.to DevOps
PostgreSQL 19's pg_stat_lock only counts waits that cross deadlock_timeout
0dev.to DevOps