How to put a number on object hallucination instead of eyeballing it
Your VLM passes general VQA evals but stakeholders complain it 'makes things up' in image descriptions. Describe how you would measure object hallucination specifically, so you can track it as a real metric rather than an anecdote.
Object hallucination is measured by comparing the objects a model claims against ground-truth labels — CHAIR scores false objects in free captions, POPE probes present/absent with yes-no questions.
Imagine a teacher checking a kid's drawing of a park against a photo of the same park. The kid says it shows a dog, a bench, and a kite. The teacher looks at the photo: bench, yes; dog, yes; kite, nope, there was no kite. So one of three things was made up. That is how you grade a vision model for making things up. You take pictures where you already know exactly what is in them, then check whether the model adds objects that were never there. You can let it describe freely and count the invented bits, or you can flat-out ask 'is there a kite?' and see if it wrongly says yes. Counting those wrong yeses gives you a real number instead of a vague feeling.
Concept explanation~2 min read
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Concept explanation~2 min read
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
When a stakeholder says a vision model 'makes things up,' they are almost never talking about a benchmark score. They are talking about reading a generated caption, glancing at the image, and noticing an object that simply is not there. The gap between that lived complaint and the green dashboard is the whole problem: a VLM can post a strong VQA or MMMU number while confidently inventing objects in nearly every description.
This deep dive is about turning that anecdote into a number you can put on a chart and gate releases on. We will cover why aggregate accuracy is the wrong instrument, the two standard measurement styles and what each one actually counts, the negative-sampling design that makes one of them a real stress test, and how to wire the result into a regression gate that survives model and decoding changes.
Why your VQA dashboard is the wrong instrument
Aggregate VQA accuracy answers one question: across many image-question pairs, how often is the model's answer correct? That metric rewards getting answers right and is completely silent on the extra material a model volunteers.
Picture a model that, on every image, correctly answers the asked question and then adds one invented object to its description. Its VQA accuracy is unchanged, because the invented object was never the thing being scored. The dashboard stays green while the product feels untrustworthy.
The core mismatch is that hallucination is a precision failure over described content, and accuracy benchmarks measure neither precision over free generation nor the absent half of the world. You need a metric whose denominator includes the objects the model could have wrongly claimed but should not have. That is a different measurement instrument, and building it is the actual task. Everything that follows is about constructing that instrument so the number it produces tracks the complaint.
Situations where this technique stops working.
2–4 min · Everything important, quickly.
Real products, models, and research that use this idea.
- GPT-5.5 and Gemini 3.1 Pro vision teams report hallucination rates separately from VQA accuracy because strong VQA scores still hide over-description
- POPE's adversarial negative sampling (co-occurring absent objects) is the standard stress split for VLM hallucination papers
What an interviewer would ask next. Try answering before peeking at the approach.
QWhy does adversarial negative sampling in POPE expose more hallucination than random sampling?
Walk through the language prior. Objects that co-occur in training data (fork next to plate, mouse next to keyboard) make the model predict yes from text statistics alone. Random absent objects are easy to reject; co-occurring absent objects pit the prior against the pixels, which is exactly the failure you want to measure.
Red flags & common mistakes
The phrases that signal junior thinking. Click to expand.
Red flags & common mistakes
The phrases that signal junior thinking. Click to expand.
Trusting overall VQA accuracy as a hallucination metric, when a model can score well on average while still confidently inventing extra objects in every description.
60 second bullets to scan on the way to the call.
Define object hallucination as asserting objects not present in the image
Explain why aggregate VQA accuracy hides this failure
Primary sources. Browse if you want the original framing.
Same topic, related formats. Practice these next.