The useful result
Resolve one disagreement between assistants with a checked source or a test, and record anything still uncertain.
- Resolve one disagreement between assistants with a checked source or a test, and record anything still uncertain.
You ask two assistants the same question and get opposite answers. Neither says “I might be wrong”. Choosing the more confident one, or the one you like, is a coin flip. Anthropic notes that inconsistent outputs across repeated runs can be a sign of hallucination, so disagreement is useful information: it tells you where to look.
The trick is to stop treating the models as judges and use them as witnesses. Pin the disagreement down to one claim, ask each witness for evidence that can be checked and for what would prove it wrong, then settle the matter yourself with a primary source or a small test.
The examples below are illustrative exercises, not recorded results from any tool. Sources were checked on 24 October 2026; menus, limits and prices change, so confirm details on the linked pages.
Before you start
- A question where two assistants gave different answers
- Access to both answers
- A search engine, official documentation or a way to run a quick test
Review evidence
Documentation-based review · 2026-10-24
Primary documentation and official guidance checked on 24 October 2026. Examples, checks and exercises are original illustrations, not recorded tool tests. Cover artwork is a conceptual illustration.
Write the disagreement as one claim
Strip out everything the answers agree on. State the exact point of conflict as a yes-or-no or a number, such as “The free plan includes export” or “the limit is 100 requests per minute”. If you cannot reduce it to one claim, split it into several.
Check your result
The disagreement is written as one claim that can be checked as true or false.
Ask each assistant for evidence and a falsifier
In a fresh chat for each, ask for the evidence behind its answer, the document where the claim should appear and what would prove it wrong. Do not tell either what the other said. Look for answers that name a specific, findable source and a clear test.
Question: [claim as a question]. Give your answer, then: 1) the exact type of source where this can be verified (for example, the official pricing page or the documentation section), 2) what would prove your answer wrong, 3) how confident you are and why. If you are not sure, say so. Do not invent links.Example / expected result
Illustrative example; not a recorded model result.
“Check the plan comparison table on the provider’s pricing page. If the Free column shows ‘Export: no’, I am wrong.”
Check your result
Each assistant has named a place to check and a way its answer could be wrong.
Settle it with the primary source or a test
Go to the official page, documentation or a small experiment and look for the answer yourself. Record the date, because facts change. If neither assistant was right, or the source is unclear, record the question as uncertain instead of picking a side.
Check your result
You have checked the primary source or run the test, and your note records the date and the result.
When it goes wrong
Both assistants can be wrong in the same way. Official pages change, so note when you checked. Do not accept a model’s claim that “both are right” without a source. For medical, legal or financial matters, consult a qualified professional.
Make it your own
Find a factual question where two assistants disagree and settle it with a primary source. Write the claim, the source and the date you checked it.
Useful next resources
Sources and review
Last checked Oct 24, 2026. Features and account limits can change. Verify important results against your original material.
Did this help you complete your task?
Tell us what needs improving. No account or private output required.
Report incorrect information or a broken linkGenius Forges Editorial
Practical AI lessons with checked sources, labelled examples and human verification.
