NeurIPS 2026 Position Paper Track

From Claims to Context

Holistic information verification requires contextual signals.

Emma Kondrup1,2 Islam Eldifrawi3,2 Tong Wu1,2 Zachary Yang2 Sebastian Sabry1,2 Michael Bronstein4,5 Jean-François Godbout6,2 Reihaneh Rabbany1,2 Shenyang Huang4
1 McGill University 2 Mila – Quebec AI Institute 3 Université de Sherbrooke 4 University of Oxford 5 AITHYRA 6 Université de Montréal
Abstract

Generative AI has made coherent, plausible content cheap to produce. That erodes the signals automated fact-checking has relied on, and leaves the field's claim-centric default mis-calibrated for today's online environments.

The context around a claim and its retrieved evidence carries information that content alone does not: its temporal grounding, its source attribution, and its position within web networks. Automated systems should consider both the claim and these contextual signals.

We develop this position along four arguments. Machine learning methods should account for the temporal nature of verification, which is limited by the evidence available at the moment it happens. Contextual signals are useful for verification broadly, particularly when retrieved evidence supports conflicting judgments, and for detecting varying degrees of verifiability, ambiguity and subjectivity in a claim. We find that such nuanced claims make up considerable proportions of popular benchmarks, and outline considerations for designing and evaluating holistic verification systems.

Holistic information verification pipeline A user submits a claim to an information verification system, which first asks whether the claim is verifiable. If not, a justification explains why: temporality, subjectivity, or lack of evidence. If it is, the system asks whether the claim is factual, using content-centric claim evaluation against evidence, and whether it is reliable, using context-aware reasoning over source attribution, track record, web topology, timing and ambiguity. Both paths feed an assessment that can be Unverifiable, True, False, Ambiguous, or another label. www CLAIM EVALUATION content-centric Compare with evidence REASONING context-aware • Source considerations: attribution, track record, web topology. • Timing of claims and events. • Ambiguity and other nuances. USER CLAIM Information Verification System VERIFIABLE? FACTUAL? JUSTIFICATION • Temporality: an event may not have occurred or be covered yet. • Subjectivity: may be an opinion. • Lack of information or evidence. RELIABLE? Assessment UNVERIF. TRUE FALSE AMBIG. …
Figure 1. The proposed holistic pipeline adds context-aware reasoning over source attribution, track record and temporality to content-centric claim evaluation. The two streams together support more nuanced outcomes than a binary score.
The position

Verify the claim and what surrounds it

Rather than focusing on individual claims' factuality, verification systems should incorporate data-driven contextual information around the claim and the retrieved evidence. Current approaches, whether supervised, semi-supervised or unsupervised, mostly rely on signals inside the text. Factuality stays necessary. It is no longer sufficient.

Source attribution

Who said the claim, and in what context? Who published the supporting or refuting evidence? Primary or secondary? Any conflict of interest?

Evolving topological context

How have the claim's source and its evidence evolved over time? Who do they cite, who cites them, and how often? Have any been compromised?

Temporality

When was the claim made, and when was it verified? When was each piece of retrieved evidence published?

§2 · Automated vs. human verification

What professional fact-checkers do differently

Expert fact-checkers select claims by public relevance and potential harm, go to primary sources, interrogate each source for credibility and time frame, triangulate, and say plainly what is known and what is uncertain. Automated pipelines diverge at every stage.

Stage
Claim detection
Evidence retrieval
Verdict decision
Communication
Human tasks
  • Select, filter and prioritize claims
  • Domain research
  • Source interrogation
  • Primary evidence
  • Temporal weighting
  • Triangulation
  • Write explanation
  • Cite sources
  • Confidence
Automated methods
  • Check-worthiness detection
  • Information retrieval
  • Relevant evidence
  • Secondary sources
  • Veracity prediction
  • Evidence alignment
  • Classification
  • Explanation generation
  • LLM justification
Lesson
Significancevs. statistical ranking
Primary & temporalvs. secondary & outdated
Uncertainty clarifiedvs. over-simplification
Traceabilityvs. post-hoc justification
Figure 2. Expert fact-checker workflows compared with automated systems, and the four places where automated approaches systematically differ from expert practice.
Argument one

Verification is constrained by its temporal context

The truth of a claim, the evidence used to assess it, and that evidence's reliability all depend on when verification happens. We separate four temporal axes. Each has its own failure mode, and a system can fail along one of them while appearing competent overall.

Axis 1

Reference time of the claim

The moment the claim's truth is anchored to. Failure: aligning evidence to the wrong period and confidently judging a different proposition.

Axis 2

Retrieval time

When evidence is fetched. Failure: rankings favor popularity over recency, so an established article can outrank a newer correction.

Axis 3

Publication time of evidence

When each piece of evidence was written. Failure: weighting outdated and recent evidence equally gives order-dependent, misleading conclusions.

Axis 4

LLM knowledge cutoff

The end of the model's training data. Failure: hallucinated or outdated answers about events past the cutoff.

Case file · The eight-second attention span · Appendix D
Claim · 2015 Average human attention span fell from 12 seconds in 2000 to 8 seconds by 2013, shorter than a goldfish's.
Time, New York Times · 2015 Supports

Reported within days, attributed to a Microsoft Canada study.

BBC investigation · 2017 Refutes

The Microsoft report did not measure attention in seconds and did not mention goldfish. The figure came from Statistic Brain, whose sources did not support it.

Not yet published

The correction does not exist at retrieval time. A 2015 verifier cannot find it.

Likely verdict True

Retrieval in 2015 surfaces only the coverage from established outlets (Axis 2).

Verdict False

Only if the system weighs the 2017 correction by its publication date instead of treating it as one more vote (Axis 3).

RAG does not resolve temporality. Retrieval surfaces recent evidence but does not make the model use it correctly. Search augmentation has proven insufficient on fast-changing or false-premise queries, and frontier reasoning models struggle with claims that require reasoning over specific time ranges.

Remedy

Build living fact-checking benchmarks

Benchmarks should reflect a changing world, as LLM evaluation already does with regularly updated sets. Because verdicts evolve, treat labels as revisable. Archive and timestamp claims and evidence, and version releases to keep results reproducible.

Argument two

Source context complements claim factuality

We augment a RAG fact-checking pipeline (OpenFactCheck's RARR and FactTool implementations) with two kinds of source context and evaluate on six widely used benchmarks. Topology gives the model the domain names of each evidence source's 1- or 2-hop neighbors over three months of the CrediBench webgraphs. Source attribution either prompts the model to reason about each source's domain and motives, or supplies a numerical domain-reliability score.

Models search the web for up to 5 rounds of 5 documents per query. Results below are for GPT-5 Mini, mean ± std over 5 seeds. Qwen3-1.7B and FactTool results are in Appendix B.

Web topologySource attribution
DatasetRAG+ 1-hop+ 2-hop+ Reasoning+ Reliability scoreBest gain
RUMORS0.70±.020.75±.010.72±.010.70±.040.70±.02+5%
LIAR0.49±.020.50±.010.50±.010.49±.010.58±.01+9%
ISOT0.49±.020.52±.020.53±.010.50±.010.54±.02+5%
ClaimsKG0.46±.010.46±.010.46±.020.47±.010.48±.01+2%
FakeCovid0.46±.030.57±.050.53±.050.47±.020.50±.05+11%
Benjamin0.63±.030.68±.040.67±.020.63±.040.62±.04+5%
Table 2. Accuracy of baseline RAG and four context augmentations. Shaded cells are the best per dataset, underlined cells the second best.

Topology helps on most benchmarks, with gains of up to 10.7% for GPT-5 Mini and 11.1% for Qwen. 1-hop and 2-hop perform comparably, which suggests most of the gain comes from adding structure at all. A numerical reliability score improves every dataset except Benjamin on GPT (up to 8.5%) and every dataset except RUMORS on Qwen (up to 12.4%). Prompted source reasoning is negligible on GPT but strong on Qwen, up to 12.2% on FakeCovid.

Source topology also matters because adversaries already exploit it: SEO manipulation and networks such as Pravda push low-quality sites into search rankings and scraping pipelines.

Remedy

Use topology-aware methods

Hyperlink structure encodes signals that content cannot recover. Combining graph neural networks or graph transformers with LLM text embeddings is a promising route to multimodal verification.

Remedy

Integrate source attribution modules

Attach context reasoning and numerical reliability signals to the retrieved evidence and to the claim itself, as fact-checking practice does. Stronger justifications can also build trust in models.

Argument three

Context can help decide which sources to trust under conflict

Conflicting evidence is common. RARR aggregates predictions made from single pieces of evidence, so we can measure directly how often the retrieved evidence disagrees. In four of the six benchmarks, more than 10% of queries do. Conflicts can be temporal (sources from different periods) or factual (sources asserting opposite facts). Current LLM-RAG pipelines rank evidence by content relevance and largely ignore credibility. Telling primary from secondary sources, which source context informs, is a first step toward resolving the conflict.

Queries with conflicting retrieved evidence
Share of queries per benchmark. Dashed line marks 10%.
Table 4. Rates of conflicting evidence across evaluated datasets (Appendix A.2).
Remedy

Use context-aware conflict resolution modules

Professional fact-checkers accept that concurrent narratives can exist. Automated systems should handle conflicting evidence in principled ways and express the disagreement or uncertainty, using context to arbitrate. The Pope case file below shows one such resolution.

Case file · 2016 · Appendix C
Claim Pope Francis endorsed Donald Trump for President of the United States. ~1M Facebook engagements before the election
WTOE5News Supports

“Pope Francis Shocks World, Endorses Donald Trump for President, Releases Statement.” Republished with the same headline on Ending the Fed.

Secondary source: reports a statement it attributes to the Vatican
Domain registered about two weeks before the story
Its own About page calls it “a fantasy news website”
Pope Francis, press conference Refutes

“I never say a word about electoral campaigns.” (2 October 2016)

Direct statement from the person the claim is about
Published by established outlets
Vatican Press Office No statement

No corresponding endorsement appears in Vatican communications. No reputable outlet reported one.

Primary source for any papal endorsement
Silence from the primary source is itself evidence
Verdict Conflicting

Matched on content alone, one article supports the claim and another refutes it. Both are fluent and on-topic, so text similarity gives no way to choose between them.

Verdict False

Two contextual moves settle it. The primary source is the Vatican Press Office, which says nothing. The only outlet reporting the endorsement is a two-week-old domain that describes itself as fantasy news.

Argument four

Subjectivity on a Spectrum: Nuances are Prevalent in Fact-Checking

A verifier that strips context can give a confident verdict on a claim that was never fully specified. We audited seven benchmarks with GPT-5 Mini plus web search for three kinds of nuance.

Unverif. no single justifiable answer Ambig. several answers, each justifiable in some context Opinion a subjective judgment, not a fact
Share of benchmark claims flagged as nuanced
Each bar sums the three categories. Most of these datasets still expect a single correct label.
Unverifiable Ambiguous Opinion
Dataset% Unverifiable% Ambiguous% Opinion
Table 3. Benchmarks show high and varied rates of nuanced claims, yet most evaluations do not account for them.
77.4%

of LIAR claims are ambiguous, even though each is scored against one correct label.

39–45%

inter-annotator agreement among five expert annotators labelling 200 claims from LIAR and ClaimsKG. Experts struggle to classify nuance too, though they report similar overall rates (Appendix A.3).

Remedy

Set comprehensive benchmarking standards

Label claims for verifiability, ambiguity and subjectivity at release, and whenever the benchmark is updated, and timestamp all claims and evidence. Models can then learn to withhold confident verdicts on unverifiable claims, and accuracy can be compared across claim types.

§4 · Alternative view

Isn't content-only verification safer?

We take the strongest counter-position seriously and answer it point by point.

The objection
  1. Genetic fallacy. Judging claims by provenance risks rejecting true claims from low-reputation sources and accepting false ones from reputable sources.
  2. Attack surface. Backlinks and citation patterns can be manipulated, as the Pravda network and SEO campaigns show.
  3. Reproducibility. A content-only verdict is reproducible from the claim and a fixed knowledge base. Context depends on an unstable web.
  4. Scale. Context needs billion-scale temporal webgraphs, reliability databases and versioned benchmarks.
Our response
  1. Combine signals. Generative models erase the discriminative power of content alone. Triangulating across channels, as experts do, means no single signal decides.
  2. Coordinated attacks cost more. Gaming content, structure and timing together is far more expensive than gaming any one channel.
  3. Knowledge bases drift too. The “fixed” baseline is itself a moving target. The answer is explicit versioning and transparent, contestable reliability signals.
  4. Scale cost to stakes. Shared resources like CrediBench and DomainDemo are spreading the infrastructure cost. Low-stakes uses can run lighter pipelines, while elections and public health justify the full stack.
Citation

Cite this work

@inproceedings{kondrup2026claims,
  title     = {From Claims to Context: Holistic Information
               Verification Requires Contextual Signals},
  author    = {Kondrup, Emma and Eldifrawi, Islam and Wu, Tong and
               Yang, Zachary and Sabry, Sebastian and Bronstein, Michael and
               Godbout, Jean-Fran{\c{c}}ois and Rabbany, Reihaneh and
               Huang, Shenyang},
  booktitle = {Advances in Neural Information Processing Systems
               (NeurIPS), Position Paper Track},
  year      = {2026}
}