Papers › Chain-of-Thought Hub: A Continuous Effort to Measure Large Language Models' Reasoning...

Chain-of-Thought Hub: A Continuous Effort to Measure Large Language Models' Reasoning Performance

26 May 2023arXiv:2305.17306archive 2025-07-28

Yao Fu, Litu Ou, Mingyu Chen, Yuhao Wan, Hao Peng, Tushar Khot

As large language models (LLMs) are continuously being developed, their evaluation becomes increasingly important yet challenging. This work proposes Chain-of-Thought Hub, an open-source evaluation suite on the multi-step reasoning capabilities of large language models. We are interested in this setting for two reasons: (1) from the behavior of GPT and PaLM model family, we observe that complex reasoning is likely to be a key differentiator between weaker and stronger LLMs; (2) we envisage large language models to become the next-generation computational platform and foster an ecosystem of LLM-based new applications, this naturally requires the foundation models to perform complex tasks that often involve the composition of linguistic and logical operations. Our approach is to compile a suite of challenging reasoning benchmarks to track the progress of LLMs. Our current results show that: (1) model scale clearly correlates with reasoning capabilities; (2) As of May 2023, Claude-v1.3 and PaLM-2 are the only two models that are comparable with GPT-4, while open-sourced models still lag behind; (3) LLaMA-65B performs closely to code-davinci-002, indicating that with successful further development such as reinforcement learning from human feedback (RLHF), it has great potential to be close to GPT-3.5-Turbo. Our results also suggest that for the open-source efforts to catch up, the community may focus more on building better base models and exploring RLHF.

PaperPDFCodeCode Syntology ran

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 9 code samples harvested from 1 repository linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 3 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 3 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 9 samples from 1 repository, 9 ran (6 with no instrument failure; 3 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-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 2 of the 9 samples that ran have no recorded date.

franxyao/chain-of-thought-hub officialmentioned in papermentioned on GitHubMITSyntology: 9 samples, 9 ran (3 instrument-failed) · 0 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

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

3ran · our draft was wrong
6ran

Licence: 2 of the 9 samples are pointer only, meaning Syntology does not serve that copy's text. For 2 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from franxyao/chain-of-thought-hub. “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.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

franxyao/chain-of-thought-hub official repository 9 samples, 9 ran (3 instrument-failed) · 0 unverified
extract_ans in 9 papers BBH/run_bbh_claude_instant_v1.0.py ran fingerprinted MIT (permissive) · 9ad0c8eaff610fe8 · report fixture: signature ans:str/0/str, mode:str/0/str · returned str · level recorded 2026-09-24
extract_ans in 9 papers BBH/run_bbh_claude_v1.3.py ran fingerprinted MIT (permissive) · 295b8fa768a029bc · report fixture: signature ans:str/0/str, mode:str/0/str · returned list · level recorded 2026-09-24
extract_ans_old BBH/run_bbh_claude_v1.3.py ran fingerprinted MIT (permissive) · f728a7b605f92e44 · report fixture: signature ans:str/0/str, mode:str/0/str · returned list · level recorded 2026-09-24
format_example in 43 papers MMLU/run_mmlu_llama.py ran · our draft was wrong MIT (permissive) · cd763eaf1ac287e7 · report fixture: signature df:DataFrame/0/?, idx:int/0/int, include_answer:bool/0/bool · returned str · level recorded, date not recorded
format_subject in 26 papers MMLU/run_mmlu_llama.py ran · our draft was wrong fingerprinted MIT (permissive) · 6ab745408cb8648b · report fixture: signature subject:str/0/str · returned str · level recorded, date not recorded
gen_prompt in 35 papers MMLU/run_mmlu_llama.py ran · our draft was wrong MIT (permissive) · 3383488ea82b6c15 · report fixture: signature train_df:DataFrame/0/?, subject:str/0/str, k:int/0/int · returned str · level recorded 2026-09-24
test_answer_mmlu_ MMLU/utils.py ran fingerprinted MIT (permissive) · 0adeff57e08a3fad · report fixture: signature pred_str:str/0/str, ans:str/0/str · returned bool · level recorded 2026-09-24
test_answer_mmlu_claude MMLU/utils.py ran fingerprinted MIT (permissive) here; the stored copy is pointer only · db42ba0a29b6cff8 · report fixture: signature pred_str:str/0/str, ans_str:str/0/str · returned bool · level recorded 2026-09-24
test_answer_mmlu_claude_instant MMLU/utils.py ran fingerprinted MIT (permissive) here; the stored copy is pointer only · ff7e01003fa98d8a · report fixture: signature pred_str:str/0/str, ans_str:str/0/str · returned bool · level recorded 2026-09-24

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Absolute Position EncodingsAdamAttentionAttention DropoutBASEBPECosine AnnealingDense ConnectionsDiscriminative Fine-TuningDropoutFocusGPTGPT-3GPT-4Label SmoothingLayer NormalizationLinear LayerLinear Warmup With Cosine AnnealingMulti-Head AttentionPaLMPosition-Wise Feed-Forward LayerResidual ConnectionSoftmaxTransformerWeight Decay

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