ChatGPT vs Claude Hallucinations: How to Compare Reliability
Both ChatGPT and Claude produce incorrect information. Here is how to test unsupported claims on your own tasks, compare their reliability fairly and keep verified sources where the next session can find them.
Updated 7 min read
Both ChatGPT and Claude hallucinate: they produce incorrect, unsupported or invented information while sounding confident. There is no publicly verified, universal ranking of which assistant hallucinates less across all task types. The more useful question is how each assistant handles uncertainty on your specific tasks. Tools like fenbs keep your verified sources and lessons in one place, so the next session starts from what was already checked rather than re-verifying the same claims.
This guide explains what hallucination looks like in practice, how to test for it on tasks you actually do, and the differences in how each assistant signals uncertainty. It does not offer an accuracy ranking, because those change with every model update and vary significantly by task type.
| Aspect | ChatGPT | Claude |
|---|---|---|
| Uncertainty signaling | Usually signals uncertainty; may still state errors confidently | Often more explicit about limits of its knowledge |
| Source access | Can cite real links with web search on; links may not match content | No web search; works from training data |
| Citation accuracy | Can hallucinate citations; web search reduces this for real pages | Can hallucinate citations; no real-time verification |
| Confident errors | Occurs in both, especially on specific facts, dates and figures | Occurs in both; Claude tends to hedge more on uncertain claims |
| Testing approach | Run on known-answer tasks and verify outputs against primary sources | Same approach: test on your tasks, verify against primary sources |
What hallucination looks like in practice
Hallucination is not always obvious. The most dangerous form is a plausible, confident-sounding claim that is slightly wrong. A date shifted by a year. A legal case cited correctly but with the wrong ruling. A statistic that is real but refers to a different country or a different year. These errors are hard to catch without checking the source.
The most visible form is an invented citation: a paper or book that does not exist, a court case that never happened, a regulation attributed to the wrong body. This kind of error is common with both assistants when asked to cite specific sources. Check every citation in the original document before using it in any professional or academic work.
A less obvious form is omission: the assistant gives a correct but incomplete answer, leaving out a qualification that changes the meaning. "This rule applies to US companies" without mentioning that it only applies to companies over a certain size. Test for this by asking follow-up questions about scope, exceptions and conditions.
How each assistant signals uncertainty
Claude tends to be more explicit about the limits of what it knows. It often signals phrases like "I'm not certain about this" or "you should verify this with the original source" before a claim it is less confident in. That signaling does not prevent errors, but it helps you know where to focus your verification effort.
ChatGPT also signals uncertainty, but the behavior varies by model version and task. In some cases it will add a caveat at the end of a paragraph rather than before the specific claim, which can make it easy to miss. Both assistants can state an incorrect fact with apparent confidence, particularly for specific numbers, dates, names and citations.
Neither assistant's self-reported confidence is a reliable proxy for accuracy. An assertion delivered with a qualifying phrase can still be wrong. An assertion delivered without one can still be right. Your own verification against the primary source remains the only reliable check.
Testing reliability on your own tasks
The most useful way to compare hallucination rates is to run both assistants on tasks with known correct answers in your own domain. Pick ten questions where you already know the right answer and where precision matters. Ask both and check. That test tells you which assistant is more reliable for your specific use case, not for a general benchmark.
For factual claims: ask each assistant to name the source of the claim. Then find that source. If the source does not exist, the claim is suspect. If the source exists but the claim misrepresents it, the assistant has produced a subtle error. Both are worth noting.
For procedural claims (how to do something, what a regulation requires, how a function works): run the steps yourself on a low-stakes test before applying them to real work. An incorrect step in a procedure is often harder to catch than an incorrect fact, because you may not know what the right answer looks like.
Save verified sources so the next session starts from confirmed facts
In fenbs, record each fact you have verified and the source where you confirmed it. When an assistant gives you a claim you need to check, verify it and save the result as a lesson or a link. The next session reads those verified facts, so you do not re-check the same claim from scratch. Add a task for any claim that still needs verification.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
ChatGPT web search and citation accuracy
When ChatGPT's web search is on, it can retrieve and link to real pages, which reduces invented citations for current content. A link to a real page is still not a guarantee that the quoted content matches what the page says. AI summaries of web content are not always accurate. Follow the link and read the relevant section yourself.
Claude does not access the web. It draws on training data with a knowledge cutoff. For recent events, current regulations or this year's statistics, Claude's training data may be incomplete or outdated. Use Claude for analysis and reasoning on material you provide, and verify facts that depend on recency separately.
Task types where each performs more reliably
- Analysis and reasoning about material you provide: both are strong, and hallucination is less common when the facts are in the prompt.
- Specific facts, dates, statistics and citations: verify these with primary sources regardless of which assistant you use.
- Recent events, current regulations, live data: ChatGPT with web search has an advantage; Claude may be out of date.
- Long structured documents (contracts, reports, detailed summaries): both are useful, but check every specific claim they add that was not in your source material.
Hallucination risk drops significantly when you put the source material in the prompt. If you paste the relevant section of a document and ask the assistant to reason about it, it is working from the material in front of it rather than from training data. That reduces the scope for invention.
Reducing hallucination risk with grounded prompts
For any task where a specific fact matters, structure the prompt to minimize reliance on the assistant's recall. Paste the relevant paragraph, clause or section and ask the assistant to reason about it, rather than asking it to recall the information from training data. The assistant works from what is in front of it rather than from memory, which significantly reduces the scope for invention in the response.
Ask the assistant to identify the weakest point in its own answer. Both ChatGPT and Claude will often flag where they are least confident when asked directly. That self-assessment is not always accurate, but it gives you a starting point for your verification effort rather than leaving you to guess which claims need checking first. For any claim that matters professionally or academically, treat that as the first place to look.
How to do this with fenbs
- Create a free account and add a project for work where verification matters: research, legal work, financial analysis or anything with factual claims.
- Add a task for each claim or section you need to verify. Note the claim, where it came from and what the verified answer is.
- Record a lesson when you catch an error. Note the type of claim that was wrong, the context and the correct source. That record helps you know where to focus verification effort in similar tasks.
- Connect your AI apps from Integrations. Ask the assistant to read your project context at the start of each session. It sees your verified facts and previous lessons before it responds.
- Use the Links and listings feature to save primary sources alongside the claims they support. That way the source is one step from the fact, not buried in a chat history.
Build a record of what each assistant gets wrong on your tasks
Record a lesson in fenbs each time you catch an error: the type of claim, the context, the actual answer and where you found it. Over time, those lessons form a guide to where each assistant is less reliable on your specific work, and which claims always need an independent check.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
What to do about hallucinations
The practical response to hallucination is a verification habit rather than a preference for one assistant. For any claim that matters: ask for the source, find the source, read the source. Use both assistants for analysis and reasoning on material you control. Rely on neither for citations or specific facts without checking.
For a broader comparison of how ChatGPT and Claude differ across tasks, see Claude vs ChatGPT. For how to move between the two while keeping verified facts intact, see switching from ChatGPT to Claude.