Papers › Generative causal testing to bridge data-driven models and scientific theories in...

Generative causal testing to bridge data-driven models and scientific theories in language neuroscience

1 Oct 2024arXiv:2410.00812archive 2025-07-28

Richard Antonello, Chandan Singh, Shailee Jain, Aliyah Hsu, Sihang Guo, Jianfeng Gao, Bin Yu, Alexander Huth

Representations from large language models are highly effective at predicting BOLD fMRI responses to language stimuli. However, these representations are largely opaque: it is unclear what features of the language stimulus drive the response in each brain area. We present generative causal testing (GCT), a framework for generating concise explanations of language selectivity in the brain from predictive models and then testing those explanations in follow-up experiments using LLM-generated stimuli.This approach is successful at explaining selectivity both in individual voxels and cortical regions of interest (ROIs), including newly identified microROIs in prefrontal cortex. We show that explanatory accuracy is closely related to the predictive power and stability of the underlying predictive models. Finally, we show that GCT can dissect fine-grained differences between brain areas with similar functional selectivity. These results demonstrate that LLMs can be used to bridge the widening gap between data-driven models and formal scientific theories.

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

By repository: official repository: 11 samples from 1 repository, 8 ran (2 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-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

microsoft/automated-explanations officialmentioned on GitHubMITSyntology: 11 samples, 8 ran (6 instrument-failed) · 3 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

11 samples harvested: 8 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 6 where Syntology's instrument failed) · 3 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.

6ran · our draft was wrong
2ran
3unverified

Licence: 0 of the 11 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 microsoft/automated-explanations. “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.

microsoft/automated-explanations official repository 11 samples, 8 ran (6 instrument-failed) · 3 unverified
abbrev_question neuro/analyze_helper.py ran · our draft was wrong fingerprinted MIT (permissive) · 310161a8ecbabb93 · report fixture: signature q:str/0/str · returned str · level recorded 2026-09-24
abbrev_questions neuro/analyze_helper.py ran · our draft was wrong MIT (permissive) · e04694cbb4b82cd5 · report fixture: signature qs:list/1/str · returned list · level recorded 2026-09-24
add_computational_args experiments/02_fit_encoding.py ran · our draft was wrong MIT (permissive) · 9bbefbf1fe49b884 · report fixture: returned ArgumentParser · level recorded 2026-09-24
add_computational_args experiments/04_fit_top_correlated_q.py ran · our draft was wrong MIT (permissive) · 51746ff4a1e417aa · report fixture: returned ArgumentParser · level recorded 2026-09-24
add_main_args experiments/04_fit_top_correlated_q.py ran · our draft was wrong MIT (permissive) · ef3c075565c3b82d · report fixture: signature parser:ArgumentParser/0/? · returned ArgumentParser · level recorded 2026-09-24
eval_acc in 15 papers experiments/03_finetune.py ran MIT (permissive) · 52cd62735dc91c81 · report fixture: signature model:callable/0/?, loader:list/1/tuple, gt_labels:ndarray/1/int · returned float64 · level recorded 2026-09-24
load_results in 82 papers neuro/analyze_helper.py ran · our draft was wrong MIT (permissive) · 989dd5f550055630 · report fixture: signature save_dir:str/0/str · returned DataFrame · level recorded 2026-09-24
retry in 14 papers neuro/agent.py ran MIT (permissive) · 06adac01803951e8 · report fixture: signature max_attempts:int/0/int, delay:float/0/float, exceptions:tuple/1/callable · returned function · level recorded 2026-09-24
call_api in 21 papers experiments/05_run_ngrams_gpt.py unverified MIT (permissive) · 91e9d8ef7d0f2766 · report
concatenate_running_texts neuro/decoding.py unverified MIT (permissive) · 5079aa51ac8e72ac · report
get_dfs experiments/03_finetune.py unverified MIT (permissive) · 5b2f99ad4deb0364 · report

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

GCT

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