5 of 5 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 3 violated it and 0 have no contract verdict; 2 failures of our instrument; 0 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.
"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2010.02840.json · badge: /api/ran/2010.02840.svg
Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.
| Repository | Role | Ran |
|---|---|---|
| taoyds/test-suite-sql-eval | canonical (classifier label) classifier basis: classifier_2025 |
2 ran · 0 no recorded run |
| copy not recorded | community not in the paper's declared repositories |
3 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| acc | Ran ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT) |
taoyds/test-suite-sql-eval/evaluate_classical.py code served (permissive licence) · get_code("bd001f76894a9867") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1) and returned float, ndim 0, dtype family float, shape () as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| condition_has_like | Ran ran, violated the contract we drafted |
this paper's copy was not recorded; identical code first harvested from taoyds/spider pointer only · get_code("8231e3fdffa9c8ee") How it ranThe body of this sample is withheld: this paper's copy of the code was not recorded (its link names no repository or source path), so no licence was read for it. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded. |
| condition_has_or | Ran ran, violated the contract we drafted |
this paper's copy was not recorded; identical code first harvested from taoyds/spider pointer only · get_code("f2d76234528d3b57") How it ranThe body of this sample is withheld: this paper's copy of the code was not recorded (its link names no repository or source path), so no licence was read for it. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded. |
| condition_has_sql | Ran ran, violated the contract we drafted |
this paper's copy was not recorded; identical code first harvested from taoyds/spider pointer only · get_code("954c76e256cc7220") How it ranThe body of this sample is withheld: this paper's copy of the code was not recorded (its link names no repository or source path), so no licence was read for it. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded. |
| load_predictions | Ran ran; our contract draft was wrong, not the code |
taoyds/test-suite-sql-eval/evaluate_classical.py code served (permissive licence) · get_code("c64a2627f38e10a8") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1) and returned list, ndim 1, dtype family float; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
Of 5 samples lifted from this paper's linked repositories, 5 carry a function identity and 0 do not. Of the 5 distinct functions with an identity, 5 are also present in other papers whose code we hold (3 with at least one paper dated earlier, 0 the same month, 5 later) and 0 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).
Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.
| Function | Also present in | Earliest-dated | Others named |
|---|---|---|---|
| condition_has_like | 14 other papers 2 dated earlier, 11 later, 1 same year, order not determinable |
1809.08887 (2018-09) Spider: A Large-Scale Human-Labeled Dataset for Complex and Cross-Domain Semantic Parsing and Text-to-SQL Task |
1906.02285 (2019-06) SParC: Cross-Domain Semantic Parsing in Context 2020.emnlp-main.564 (2020 (year only)) Re-examining the Role of Schema Linking in Text-to-SQL and 11 more not named here |
| condition_has_or | 14 other papers 2 dated earlier, 11 later, 1 same year, order not determinable |
1809.08887 (2018-09) Spider: A Large-Scale Human-Labeled Dataset for Complex and Cross-Domain Semantic Parsing and Text-to-SQL Task |
1906.02285 (2019-06) SParC: Cross-Domain Semantic Parsing in Context 2020.emnlp-main.564 (2020 (year only)) Re-examining the Role of Schema Linking in Text-to-SQL and 11 more not named here |
| condition_has_sql | 11 other papers 2 dated earlier, 8 later, 1 same year, order not determinable |
1809.08887 (2018-09) Spider: A Large-Scale Human-Labeled Dataset for Complex and Cross-Domain Semantic Parsing and Text-to-SQL Task |
1906.02285 (2019-06) SParC: Cross-Domain Semantic Parsing in Context 2020.emnlp-main.564 (2020 (year only)) Re-examining the Role of Schema Linking in Text-to-SQL and 8 more not named here |
| acc | 1 other paper 1 later |
2505.14305 (2025-05) JOLT-SQL: Joint Loss Tuning of Text-to-SQL with Confusion-aware Noisy Schema Sampling |
|
| load_predictions | 1 other paper 1 later |
2505.14305 (2025-05) JOLT-SQL: Joint Loss Tuning of Text-to-SQL with Confusion-aware Noisy Schema Sampling |
Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.
Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.
We propose test suite accuracy to approximate semantic accuracy for Text-to-SQL models. Our method distills a small test suite of databases that achieves high code coverage for the gold query from a large number of randomly generated databases. At evaluation time, it computes the denotation accuracy of the predicted queries on the distilled test suite, hence calculating a tight upper-bound for semantic accuracy efficiently. We use our proposed method to evaluate 21 models submitted to the Spider leader board and manually verify that our method is always correct on 100 examples. In contrast, the current Spider metric leads to a 2.5% false negative rate on average and 8.1% in the worst case, indicating that test suite accuracy is needed. Our implementation, along with distilled test suites for eleven Text-to-SQL datasets, is publicly available.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2010.02840")
get_code_for_paper("2010.02840")
have("2010.02840")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2010.02840.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2010.02840)
Connect an agent — have() is free.