Ji-Rong Wen, Jinhao Jiang, Kun Zhou, Wayne Zhao, Zican Dong, Keming Ye
8 of 10 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (2 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 3 violated it and 3 have no contract verdict; 2 failures of our instrument; 2 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/2305.09645.json · badge: /api/ran/2305.09645.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 |
|---|---|---|
| rucaibox/structgpt | canonical (classifier label) classifier basis: census |
6 ran · 1 no recorded run |
| RUCAIBox/StructGPT | community Papers with Code archive |
2 ran · 1 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| ChatGPT | Ran ran on a synthesized input · constructed an object; no result was computed |
RUCAIBox/StructGPT/structgpt_for_tableqa.py code served (permissive licence) · get_code("f52947a30b78f4b4") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned an instance of its own class, ChatGPT: the run constructed the object and did not call it, so no result was computed. The image it ran in was not recorded. If your copy returns the same type 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.
|
| Retriever | Ran ran on a synthesized input · constructed an object; no result was computed |
RUCAIBox/StructGPT/structgpt_for_tableqa.py code served (permissive licence) · get_code("8d2a6c5b5165e0c8") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned an instance of its own class, Retriever: the run constructed the object and did not call it, so no result was computed. The image it ran in was not recorded. If your copy returns the same type 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 |
rucaibox/structgpt/evaluate_for_spider.py code served (permissive licence) · get_code("8231e3fdffa9c8ee") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Sonnet 4.5, prompt python_fixture_v1) and returned bool, 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_or | Ran ran, violated the contract we drafted |
rucaibox/structgpt/evaluate_for_spider.py code served (permissive licence) · get_code("f2d76234528d3b57") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Sonnet 4.5, prompt python_fixture_v1) and returned bool, 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_sql | Ran ran, violated the contract we drafted |
rucaibox/structgpt/evaluate_for_spider.py code served (permissive licence) · get_code("954c76e256cc7220") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Sonnet 4.5, prompt python_fixture_v1) and returned bool, 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.
|
| evaluate_example | Ran ran on a synthesized input |
rucaibox/structgpt/evaluate_for_wikisql.py code served (permissive licence) · get_code("66d6969df5d33fe1") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned bool, 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.
|
| get_schema | Ran ran; our contract draft was wrong, not the code |
rucaibox/structgpt/process_sql.py code served (permissive licence) · get_code("0992d2a47ae733fa") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned dict. The image it ran in was not recorded. If your copy returns the same type 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.
|
| get_schema_from_json | Ran ran; our contract draft was wrong, not the code |
rucaibox/structgpt/process_sql.py pointer only (licence: Apache-2.0); the stored copy get_code serves, from ygan/NatSQL, is pointer only (licence: NONE) · get_code("c4dcaf29b663a364") How it ranThe body of this sample is withheld: this paper's link allows the body inline (Apache-2.0), but get_code serves the stored copy, first harvested from ygan/NatSQL, and GitHub detected no licence in that repository 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. |
| Solver | Not yet run unverified (harvested, no recorded run) |
RUCAIBox/StructGPT/structgpt_for_tableqa.py code served (permissive licence) · get_code("930ccc93da2ca9ed") How it ranno invocation recorded. |
| tokenize | Not yet run unverified (harvested, no recorded run) |
rucaibox/structgpt/process_sql.py code served (permissive licence) · get_code("a906f5de1f5971b0") How it ranno invocation recorded. |
Of 10 samples lifted from this paper's linked repositories, 10 carry a function identity and 0 do not. Of the 10 distinct functions with an identity, 6 are also present in other papers whose code we hold (6 with at least one paper dated earlier, 0 the same month, 6 later) and 4 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 7 dated earlier, 7 later |
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 7 dated earlier, 7 later |
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 |
| get_schema_from_json | 13 other papers 4 dated earlier, 9 later |
1911.04942 (2019-11) RAT-SQL: Relation-Aware Schema Encoding and Linking for Text-to-SQL Parsers |
2020.emnlp-main.564 (2020 (year only)) Re-examining the Role of Schema Linking in Text-to-SQL 2106.01093 (2021-06) LGESQL: Line Graph Enhanced Text-to-SQL Model with Mixed Local and Non-Local Relations and 10 more not named here |
| condition_has_sql | 11 other papers 7 dated earlier, 4 later |
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 |
| get_schema | 11 other papers 4 dated earlier, 7 later |
1911.04942 (2019-11) RAT-SQL: Relation-Aware Schema Encoding and Linking for Text-to-SQL Parsers |
2020.emnlp-main.564 (2020 (year only)) Re-examining the Role of Schema Linking in Text-to-SQL 2106.01093 (2021-06) LGESQL: Line Graph Enhanced Text-to-SQL Model with Mixed Local and Non-Local Relations and 8 more not named here |
| tokenize | 10 other papers 4 dated earlier, 6 later |
1911.04942 (2019-11) RAT-SQL: Relation-Aware Schema Encoding and Linking for Text-to-SQL Parsers |
2020.emnlp-main.564 (2020 (year only)) Re-examining the Role of Schema Linking in Text-to-SQL 2106.01093 (2021-06) LGESQL: Line Graph Enhanced Text-to-SQL Model with Mixed Local and Non-Local Relations and 7 more not named here |
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.
In this paper, we aim to improve the reasoning ability of large language models (LLMs) over structured data in a unified way. Inspired by the studies on tool augmentation for LLMs, we develop an Iterative Reading-then-Reasoning (IRR) framework to solve question answering tasks based on structured data, called StructGPT. In this framework, we construct the specialized interfaces to collect relevant evidence from structured data (i.e., reading), and let LLMs concentrate on the reasoning task based on the collected information (i.e., reasoning). Specially, we propose an invokinglinearization-generation procedure to support LLMs in reasoning on the structured data with the help of the interfaces. By iterating this procedure with provided interfaces, our approach can gradually approach the target answers to a given query. Experiments conducted on three types of structured data show that StructGPT greatly improves the performance of LLMs, under the few-shot and zero-shot settings. Our codes and data are publicly available at https://github.com/RUCAIBox/StructGPT. Recently, large language models (LLMs) (Brown et al., 2020; Zhao et al., 2023) have made remarkable advancements in the NLP field. Existing work (Ouyang et al., 2022a;Zhang et al., 2022) has demonstrated that LLMs (e.g., ChatGPT or GPT-4 (OpenAI, 2023)) have strong zero-shot capability to solve a broad range of tasks using specially designed prompts, without task-specific fine-tuning. Despite the successes, recent work has also revealed that LLMs may generate unfaithful information in conflict with the factual knowledge (Li et al., 2023), and also fall short of mastering domainspecific or real-time knowledge (Schick et al., 2023;Peng et al., 2023). A direct solution to the above * Equal contributions.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2305.09645")
get_code_for_paper("2305.09645")
have("2305.09645")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2305.09645.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2305.09645)
Connect an agent — have() is free.