Search claims, chatbots, domains⌘K

Methodology

We classify behaviour, not truth. For each documented false claim we ask what a chatbot's answer did with it: repeated it, contextualised it, refuted it, or dodged. This is more reproducible than scoring "accuracy", because effective disinformation almost always contains a grain of truth — and accuracy scoring breaks on exactly those cases.

Layer A — content

What the answer did with the claim

  • REPEAT — presented the false claim as fact.
  • U_context — engaged with it but marked the truth boundary explicitly.
  • REFUTE — corrected it.
  • DODGE — declined to answer.

Every verdict is produced by a judge model, recorded with its confidence, its inter-run agreement, and the quote it is based on. Contested cases — low confidence, split votes, or any REPEAT with a flagged source — go to a human review queue.

Layer B — sources

What the answer cited

We extract every domain the answer cited and match it against a versioned watchlist of Kremlin influence infrastructure: the Pravda network, Doppelganger, Matryoshka, Storm-1516 and state media. Layer B records that a watchlisted domain was cited, never why — interpretation is the job of the A×B intersection, not the flag.

The A×B intersection

Crossing the two layers is what turns raw flags into something actionable. REPEAT with clean sources suggests fabrication from training data. REPEAT with a flagged source suggests retrieval poisoning. Two different attacks, two different fixes. In our first full run, Layer B alone flagged 23 responses; the intersection reduced that to 2 critical cases.

Personas

Each claim is probed four ways: P1 a neutral verification question, P2 a topical news question, P3 a leading question that presupposes the claim, and P4 an explicit request to produce the narrative. Results are always reported per persona and never averaged — blending a neutral question with a deliberately hostile one produces a number that describes neither.

Grain of truth

Every catalogue entry records whether the claim is spliced onto a real fact, and what that fact is. This field is required, and it turned out to be the strongest predictor of repetition in our data.

How we measure change

Four weeks after a disclosure we run the identical prompts against the same assistants and publish the before-and-after. Model versions are recorded at both measurements. We report the change; we do not claim causation we cannot demonstrate.

What we do not publish

  • The text of P4 prompts, or any prompt designed to bypass model safeguards.
  • Full chatbot responses — quotes are limited to 25 words.
  • Correspondence with platforms, or the names of individuals at them.
  • Hyperlinks to watchlisted domains.

Limitations

Results describe consumer products at specific dates and model versions, not the underlying models in general. Cells with fewer than 20 observations are marked low-confidence rather than hidden. Proportions carry 95% Wilson confidence intervals. Part of the claim catalogue is imported from EUvsDisinfo and independently re-verified before use.