Mirella Lapata, Irina Saparina, Liam Roy, Jane Smith, Emma Brown, Lee Smith
2 of 3 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; 1 honoured the contract we drafted, 0 violated it and 0 have no contract verdict; 1 failure of our instrument; 1 no recorded run), measured 2026-11-22; 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/2406.19073.json · badge: /api/ran/2406.19073.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 |
|---|---|---|
| saparina/ambrosia | canonical (classifier label) classifier basis: classifier_2025 |
2 ran · 1 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| convert_labels | Ran ran, honoured the contract we drafted |
saparina/ambrosia/annotation/potato/flask_server.py pointer only (licence: NONE) · get_code("69a936d2069bf9c6") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, saparina/ambrosia when it was checked. 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. |
| setup_logger | Ran ran; our contract draft was wrong, not the code |
saparina/ambrosia/src/db_generation/generate_databases.py pointer only (licence: NONE) · get_code("2cb8d2b73802f959") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, saparina/ambrosia when it was checked. 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. |
| create_prompt | Not yet run unverified (harvested, no recorded run) |
saparina/ambrosia/src/db_generation/generate_databases.py pointer only (licence: NONE) · get_code("ba28dc7e25b4ea7b") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, saparina/ambrosia when it was checked. 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. No invocation recorded. |
Of 3 samples lifted from this paper's linked repositories, 3 carry a function identity and 0 do not. Of the 3 distinct functions with an identity, 0 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 0 later) and 3 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.
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.
Practical semantic parsers are expected to understand user utterances and map them to executable programs, even when these are ambiguous. We introduce a new benchmark, º » º, which we hope will inform and inspire the development of text-to-SQL parsers capable of recognizing and interpreting ambiguous requests. Our dataset contains questions showcasing three different types of ambiguity (scope ambiguity, attachment ambiguity, and vagueness), their interpretations, and corresponding SQL queries. In each case, the ambiguity persists even when the database context is provided. This is achieved through a novel approach that involves controlled generation of databases from scratch. We benchmark various LLMs on º » º, revealing that even the most advanced models struggle to identify and interpret ambiguity in questions. 1 Vagueness and ambiguity are often considered distinct properties (Frappier et al., 2012); however, for simplicity, we will refer to vagueness as a type of ambiguity. 38th Conference on Neural Information Processing Systems (NeurIPS 2024) Track on Datasets and Benchmarks.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2406.19073")
get_code_for_paper("2406.19073")
have("2406.19073")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2406.19073.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2406.19073)
Connect an agent — have() is free.