Unverified50% confidenceBenchmarkExact time
On both datasets, the number of queries in which schemagate actually read a forbidden column was 0.
1
Sources
50%
Confidence
Short-term (~14 days)
Relevance
10/17/2026
First Seen
Valid until: 10/31/2026
Sources
Related Entities
Related Claims
UnverifiedBy adding to the prompt 'you are seeing part of this database; if you need more information, refuse to answer', schemagate reduced incorrect answers from 16% to 5% in a 100-question pilot.68% similarUnverifiedOn both the BIRD and Spider datasets, no SQL reading forbidden data appeared in schemagate.66% similarUnverifiedschemagate performs a policy check on each generated query before execution, and removing this step doubles the violation rate.61% similarUnverifiedWhen a data row is composed entirely of non-top-left cells of a merge, reading by row yields all nulls, causing that row to be discarded by empty-row filtering logic.60% similarUnverifiedTraditional retrieval evaluation datasets often have only single-digit relevant document annotations per query.60% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1051146API
curl https://kongchang.com/api/v1/knowledge/claims/1051146MCP
get_claim(id=1051146)