Don't Trust Confident Specifics Without Checking
What it is
The mistake of taking Claude's most confident-sounding specifics — exact figures, quotes, citations, API names, legal or medical claims — at face value because the fluent, assured tone reads as authority. Confidence is a property of the prose, not evidence the fact is right.
Why it works
Language models generate the most plausible continuation, and a plausible-sounding number, source, or method is exactly what they're built to produce — whether or not it's true. The failure is quiet: no error, no hedge, just a specific stated as if settled. The fix isn't distrust of everything but calibrated checking — verify hardest where a fact is both easy to check and costly to get wrong, and treat unverifiable confident specifics as leads, not conclusions.
When to use it
Whenever output includes checkable specifics that feed a decision, get published, or carry real consequences — citations, statistics, API signatures, dosages, legal claims, quoted figures.
When not to use it
Low-stakes, easily-reversible, or clearly-drafting contexts where a wrong specific costs nothing and you'll catch it downstream anyway. Calibrate the effort to the stakes.
Prompt
For this answer, mark every specific claim — numbers, names, citations, dates, API signatures — with how sure you are and whether you're recalling it or inferring it. List the ones I should independently verify before relying on them, hardest-to-be-sure-of first. Don't soften; flag your own weak spots.Example
A market-size figure and a cited study look authoritative in a draft; asked to flag its own specifics, Claude marks both as 'recalled, verify' — and the study turns out not to exist. You catch it before it ships instead of after a reader does.
Advanced version
For consequential facts, give Claude the source material and have it answer only from what you provided, quoting the supporting line for each claim. Grounding plus a citation you can check beats recall you have to trust.
Common mistakes
- Reading fluency as accuracy and shipping unverified specifics.
- Over-correcting into distrust of everything, which wastes the tool's real value.
- Not asking the model to separate recall from inference, when it will if you ask.