Barbara Plank, Philipp Mondorf
5 of 6 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; 0 honoured the contract we drafted, 1 violated it and 0 have no contract verdict; 4 failures 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/2402.14856.json · badge: /api/ran/2402.14856.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 |
|---|---|---|
| mainlp/inferential-strategies | canonical (classifier label) classifier basis: census |
5 ran · 1 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| draw_adjective | Ran ran; our contract draft was wrong, not the code |
mainlp/inferential-strategies/reasoning_strategies/dataprep/preprocessing.py pointer only (licence: CC-BY-SA-4.0) · get_code("c9e9d679ca961f0b") How it ranThe body of this sample is withheld: CC-BY-SA-4.0, as GitHub detects it on this paper's repository, mainlp/inferential-strategies, is not in the permissive set Syntology serves inline. 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. |
| load_data_from_json | Ran ran; our contract draft was wrong, not the code |
mainlp/inferential-strategies/reasoning_strategies/utils/utils.py pointer only (licence: CC-BY-SA-4.0) · get_code("a8487406395eacf9") How it ranThe body of this sample is withheld: CC-BY-SA-4.0, as GitHub detects it on this paper's repository, mainlp/inferential-strategies, is not in the permissive set Syntology serves inline. 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. |
| read_yaml_file | Ran ran; our contract draft was wrong, not the code |
mainlp/inferential-strategies/reasoning_strategies/utils/utils.py pointer only (licence: CC-BY-SA-4.0) · get_code("3f821e04d5d9a0fe") How it ranThe body of this sample is withheld: CC-BY-SA-4.0, as GitHub detects it on this paper's repository, mainlp/inferential-strategies, is not in the permissive set Syntology serves inline. 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. |
| replace_words | Ran ran; our contract draft was wrong, not the code |
mainlp/inferential-strategies/reasoning_strategies/dataprep/preprocessing.py pointer only (licence: CC-BY-SA-4.0) · get_code("f496812cd5145189") How it ranThe body of this sample is withheld: CC-BY-SA-4.0, as GitHub detects it on this paper's repository, mainlp/inferential-strategies, is not in the permissive set Syntology serves inline. 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. |
| starts_with_vowel_sound | Ran ran, violated the contract we drafted |
mainlp/inferential-strategies/reasoning_strategies/dataprep/preprocessing.py pointer only (licence: CC-BY-SA-4.0) · get_code("8810006d72cdb240") How it ranThe body of this sample is withheld: CC-BY-SA-4.0, as GitHub detects it on this paper's repository, mainlp/inferential-strategies, is not in the permissive set Syntology serves inline. 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. |
| read_text_file | Not yet run unverified (harvested, no recorded run) |
mainlp/inferential-strategies/reasoning_strategies/utils/utils.py pointer only (licence: CC-BY-SA-4.0); the stored copy get_code serves, from mainlp/TruthQuest, is pointer only (licence: CC-BY-SA-4.0) · get_code("c387ce2fd70d9c06") How it ranThe body of this sample is withheld: CC-BY-SA-4.0, as GitHub detects it on this paper's repository, mainlp/inferential-strategies, is not in the permissive set Syntology serves inline. 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 6 samples lifted from this paper's linked repositories, 6 carry a function identity and 0 do not. Of the 6 distinct functions with an identity, 2 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 2 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 |
|---|---|---|---|
| read_text_file | 1 other paper 1 later |
2406.12546 (2024-06) Liar, Liar, Logical Mire: A Benchmark for Suppositional Reasoning in Large Language Models |
|
| read_yaml_file | 1 other paper 1 later |
2406.12546 (2024-06) Liar, Liar, Logical Mire: A Benchmark for Suppositional Reasoning in Large Language Models |
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.
Deductive reasoning plays a pivotal role in the formulation of sound and cohesive arguments. It allows individuals to draw conclusions that logically follow, given the truth value of the information provided. Recent progress in the domain of large language models (LLMs) has showcased their capability in executing deductive reasoning tasks. Nonetheless, a significant portion of research primarily assesses the accuracy of LLMs in solving such tasks, often overlooking a deeper analysis of their reasoning behavior. In this study, we draw upon principles from cognitive psychology to examine inferential strategies employed by LLMs, through a detailed evaluation of their responses to propositional logic problems. Our findings indicate that LLMs display reasoning patterns akin to those observed in humans, including strategies like supposition following or chain construction. Moreover, our research demonstrates that the architecture and scale of the model significantly affect its preferred method of reasoning, with more advanced models tending to adopt strategies more frequently than less sophisticated ones. Importantly, we assert that a model's accuracy, that is the correctness of its final conclusion, does not necessarily reflect the validity of its reasoning process. This distinction underscores the necessity for more nuanced evaluation procedures in the field. Evaluate whether the given conclusion logically follows from the premises below: 1. There is a blue marble if and only if there is a white marble. 2. Either there is a white marble or else there is a red marble, but not both. 3. There is a red marble if and only if there is a pink marble. Conclusion: If there is a blue marble then there is a pink marble. Statements: 1. Either there is a white marble in the box or else there is a black marble in the box, but not both. 2. Either there is a black marble in the box or else there is a pink marble in the box, but not both. 3. There is a pink marble in the box if and only if there is a gray marble in the box. Conclusion: If there is a white marble in the box then there is a gray marble in the box. Sure, I'd be happy to help! Here's my reasoning process for this problem: 1. First, I'll start by analyzing the given statements: From Statement 1, we know that the box contains either a white marble or a black marble, but not both. From Statement 2, we know that the box contains either a black marble or a pink marble, but not both. From Statement 3, we know that if there is a pink marble in the box, then there must be a gray marble in the box. 2. Now, let's consider the conclusion: If there is a white marble in the box then there is a gray marble in the box. Can we logically deduce this conclusion from the given statements? Well, if there is a white marble in the box, then by Statement 1, there cannot be a black marble in the box. If there is no black marble in the box, then by Statement 2, there must be a pink marble in the box. But if there is a pink marble in the box, then by Statement 3, there must be a gray marble in the box. So, yes, we can logically deduce the conclusion that if there is a white marble in the box, then there is a gray marble in the box.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2402.14856")
get_code_for_paper("2402.14856")
have("2402.14856")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2402.14856.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2402.14856)
Connect an agent — have() is free.