Papers › Chain-of-Table: Evolving Tables in the Reasoning Chain for Table Understanding

Chain-of-Table: Evolving Tables in the Reasoning Chain for Table Understanding

9 Jan 2024arXiv:2401.04398archive 2025-07-28

Zilong Wang, Hao Zhang, Chun-Liang Li, Julian Martin Eisenschlos, Vincent Perot, Zifeng Wang, Lesly Miculicich, Yasuhisa Fujii, Jingbo Shang, Chen-Yu Lee, Tomas Pfister

Table-based reasoning with large language models (LLMs) is a promising direction to tackle many table understanding tasks, such as table-based question answering and fact verification. Compared with generic reasoning, table-based reasoning requires the extraction of underlying semantics from both free-form questions and semi-structured tabular data. Chain-of-Thought and its similar approaches incorporate the reasoning chain in the form of textual context, but it is still an open question how to effectively leverage tabular data in the reasoning chain. We propose the Chain-of-Table framework, where tabular data is explicitly used in the reasoning chain as a proxy for intermediate thoughts. Specifically, we guide LLMs using in-context learning to iteratively generate operations and update the table to represent a tabular reasoning chain. LLMs can therefore dynamically plan the next operation based on the results of the previous ones. This continuous evolution of the table forms a chain, showing the reasoning process for a given tabular problem. The chain carries structured information of the intermediate results, enabling more accurate and reliable predictions. Chain-of-Table achieves new state-of-the-art performance on WikiTQ, FeTaQA, and TabFact benchmarks across multiple LLM choices.

PaperPDFCodeCode Syntology ranMethod as code

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 8 code samples harvested from 1 repository linked to this paper: 6 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 6 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 6 where our contract draft was wrong; failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code.

By repository: community (archive-listed): 8 samples from 1 repository, 6 ran (0 with no instrument failure; 6 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

cyqiq/multicot mentioned on GitHubSyntology: not harvested report
google-research/chain-of-table mentioned on GitHubSyntology: 8 samples, 6 ran (6 instrument-failed) · 2 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

8 samples harvested: 6 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 6 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

6ran · our draft was wrong
2unverified

Licence: 0 of the 8 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from google-research/chain-of-table. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

google-research/chain-of-table community (archive-listed) 8 samples, 6 ran (6 instrument-failed) · 2 unverified
get_act_func utils/chain.py ran · our draft was wrong Apache-2.0 (permissive) · 45acaa0c0daeb958 · report fixture: signature name:str/0/str · returned function · level recorded 2026-09-22
get_all_operation_names utils/chain.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) · 4f44bc316c51d136 · report fixture: signature string:str/0/str · returned list · level recorded 2026-09-22
get_operation_name utils/chain.py ran · our draft was wrong Apache-2.0 (permissive) · 12b7d0b6f145ce34 · report fixture: signature string:str/0/str · returned str · level recorded 2026-09-22
get_table_info utils/chain.py ran · our draft was wrong Apache-2.0 (permissive) · 300d8824cd24e444 · report fixture: signature sample:dict/0/?, skip_op:list/1/empty, first_n_op:NoneType/0/? · returned dict · level recorded 2026-09-22
table2df utils/chain.py ran · our draft was wrong Apache-2.0 (permissive) · 1a98c777eabd7e23 · report fixture: signature table_text:list/1/list, num_rows:int/0/int · returned DataFrame · level recorded 2026-09-22
table2string utils/chain.py ran · our draft was wrong Apache-2.0 (permissive) · 3f48a6cd327ba279 · report fixture: signature table_text:list/1/list, num_rows:int/0/int, caption:str/0/str · returned str · level recorded 2026-09-22
dynamic_chain_exec_one_sample utils/chain.py unverified Apache-2.0 (permissive) · 3dd6e932075d3fbc · report
generate_prompt_for_next_step utils/chain.py unverified Apache-2.0 (permissive) · 841fa5034671ee1b · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for CHAIN-OF-TABLE (graph method: CHAIN-OF-TABLE). 8 bricks; individually on a fixture: 6 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 6 where Syntology's instrument failed) · 2 unverified. The assembly has not been run end-to-end.

  1. dynamic_chain_exec_one_sample entry · level 0 · unverified · 3dd6e932075d3fbc
  2. generate_prompt_for_next_step model · level 0 · unverified · 841fa5034671ee1b
  3. get_table_info helper · level 1 · ran · our draft was wrong · 300d8824cd24e444
  4. get_all_operation_names helper · level 1 · ran · our draft was wrong · 4f44bc316c51d136
  5. get_operation_name helper · level 1 · ran · our draft was wrong · 12b7d0b6f145ce34
  6. table2string helper · level 1 · ran · our draft was wrong · 3f48a6cd327ba279
  7. get_act_func helper · level 1 · ran · our draft was wrong · 45acaa0c0daeb958
  8. table2df helper · level 1 · ran · our draft was wrong · 1a98c777eabd7e23

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2401.04398") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Fact VerificationIn-Context LearningQuestion AnsweringSemantic ParsingTable-based Fact VerificationTable-based Question Answering

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Semantic Parsing WikiTableQuestions Chain-of-Table Accuracy (Dev) / #8 of 22 Archive leaderboard report
Semantic Parsing WikiTableQuestions Chain-of-Table Accuracy (Test) 67.31 #8 of 22 Archive leaderboard report
Table-based Fact Verification TabFact Chain-of-Table Test 86.61 #4 of 15 Archive leaderboard report
Table-based Fact Verification TabFact Chain-of-Table Val - #4 of 15 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections