SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2402.10528 · 2024

Can We Verify Step by Step for Incorrect Answer Detection?

arXiv · PDF · Open in the Atlas

Code that ran

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; 1 honoured the contract we drafted, 0 violated it and 0 have no contract verdict; 4 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/2402.10528.json · badge: /api/ran/2402.10528.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.

RepositoryRoleRan
xinxu-ustc/r2pe canonical (classifier label)
classifier basis: census
5 ran · 0 no recorded run
FunctionStatusWhere it lives
card_to_name Ran
ran; our contract draft was wrong, not the code
xinxu-ustc/r2pe/nli.py
pointer only (licence: NONE) · get_code("db7f9bf2c56eba82")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, xinxu-ustc/r2pe 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.

find_most_frequent Ran
ran; our contract draft was wrong, not the code
xinxu-ustc/r2pe/runner.py
pointer only (licence: NONE) · get_code("92f36acfeb83574c")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, xinxu-ustc/r2pe 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.

get_neutral_idx Ran
ran, honoured the contract we drafted
xinxu-ustc/r2pe/nli.py
pointer only (licence: NONE) · get_code("ea7a5375f9985efb")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, xinxu-ustc/r2pe 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.

name_to_card Ran
ran; our contract draft was wrong, not the code
xinxu-ustc/r2pe/nli.py
pointer only (licence: NONE) · get_code("336a19c3f0f872cf")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, xinxu-ustc/r2pe 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.

readjsonl2list Ran
ran; our contract draft was wrong, not the code
xinxu-ustc/r2pe/runner.py
pointer only (licence: NONE); the stored copy get_code serves, from thunlp/StudyBench, is pointer only (licence: NONE) · get_code("024ac62b35bdff98")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, xinxu-ustc/r2pe 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.

Also present in other papers' code

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, 4 are also present in other papers whose code we hold (3 with at least one paper dated earlier, 0 the same month, 4 later) and 1 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.

FunctionAlso present inEarliest-datedOthers named
card_to_name 2 other papers
1 dated earlier, 1 later
2111.09525 (2021-11)
SummaC: Re-Visiting NLI-based Models for Inconsistency Detection in Summarization
2601.23183 (2026-01)
JobResQA: A Benchmark for LLM Machine Reading Comprehension on Multilingual Résumés and JDs
get_neutral_idx 2 other papers
1 dated earlier, 1 later
2111.09525 (2021-11)
SummaC: Re-Visiting NLI-based Models for Inconsistency Detection in Summarization
2601.23183 (2026-01)
JobResQA: A Benchmark for LLM Machine Reading Comprehension on Multilingual Résumés and JDs
name_to_card 2 other papers
1 dated earlier, 1 later
2111.09525 (2021-11)
SummaC: Re-Visiting NLI-based Models for Inconsistency Detection in Summarization
2601.23183 (2026-01)
JobResQA: A Benchmark for LLM Machine Reading Comprehension on Multilingual Résumés and JDs
readjsonl2list 1 other paper
1 later
2609.00787 (2026-09)
StudyBench: Can Self-Evolution Squeeze Textbooks for Olympiad Capability?

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.

Repositories linked to this paper

Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.

Abstract

Chain-of-Thought (CoT) prompting has marked a significant advancement in enhancing the reasoning capabilities of large language models (LLMs). Previous studies have developed various extensions of CoT, which focus primarily on enhancing end-task performance. In addition, there has been research on assessing the quality of reasoning chains in CoT. This raises an intriguing question: Is it possible to predict the accuracy of LLM outputs by scrutinizing the reasoning chains they generate? To answer this research question, we introduce a benchmark, R2PE, designed specifically to explore the relationship between reasoning chains and performance in various reasoning tasks spanning five different domains. This benchmark aims to measure the falsehood of the final output of LLMs based on the reasoning steps. To make full use of information in multiple reasoning chains, we propose the process discernibility score (PDS) framework that beats the answer-checking baseline by a large margin. Concretely, this resulted in an average of $5.1\%$ increase in the F1 score and $2.97\%$ improvement in AUC-PR across all 45 subsets within R2PE. We further demonstrate our PDS's efficacy in advancing open-domain QA accuracy.

For agents

The same record, over MCP at https://syntology.ai/mcp:

get_harvested_code_for_paper("2402.10528")
get_code_for_paper("2402.10528")
have("2402.10528")

The run record, dated, one paper per request, free:

curl https://syntology.ai/api/ran/2402.10528.json

A badge for a README (the split and the date, never a ratio):

[![Syntology run record](https://syntology.ai/api/ran/2402.10528.svg)](https://syntology.ai/paper/2402.10528)

Connect an agent — have() is free.