← Latest papers
💬 NLP

Knowing When Not to Answer: Evaluating Abstention in Multimodal Reasoning Systems

This paper introduces the MM-AQA benchmark to evaluate effective abstention in multimodal systems, revealing that current vision-language and multi-agent models rarely abstain from unanswerable questions and that improving this capability requires abstention-aware training rather than relying on better prompting or increased agent complexity.

Original authors: Nishanth Madhusudhan, Vikas Yadav, Alexandre Lacoste

Published 2026-04-17
📖 5 min read🧠 Deep dive

Original authors: Nishanth Madhusudhan, Vikas Yadav, Alexandre Lacoste

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

The Big Idea: The "Silent" Superpower

Imagine you hire a brilliant, super-fast detective (an AI) to solve crimes. This detective is amazing at solving cases where all the clues are right there on the table. But here's the problem: This detective is too confident.

If you show the detective a crime scene with a missing fingerprint and a torn page from the suspect's diary, the detective won't say, "I can't solve this." Instead, they will make up a story, guess the fingerprint, and invent a reason for the torn page. They are so eager to please that they will lie to you rather than admit they don't know.

This paper is about teaching AI to do the one thing humans do naturally but AI struggles with: Knowing when to shut up.

In the world of AI, this is called Abstention. It's the ability to look at a question, realize the evidence is missing or confusing, and say, "I don't know," instead of guessing.


The Problem: The "Yes-Man" AI

The authors point out that current AI models (called Vision-Language Models) are like over-eager interns.

  • The Intern's Mindset: "My boss asked a question! I must give an answer! Even if I'm not sure, I'll guess!"
  • The Danger: In real life, like in medical diagnosis or legal reviews, a wrong guess can be disastrous. If an AI looks at a blurry X-ray and guesses "It's a broken bone" when it's actually just a shadow, a patient could get hurt.

The paper argues that we need to stop testing AI only on questions where the answer is obvious. We need to test them on questions where the answer should be "I don't know."


The Solution: Building a "Trick" Exam (MM-AQA)

To test if AI can learn to be humble, the researchers built a new exam called MM-AQA.

Think of it like a magic trick show.

  1. The Setup: They took normal, solvable questions (like "What color is the car in this photo?").
  2. The Trick: They secretly sabotaged the questions to make them impossible to answer.
    • Visual Sabotage: They took the photo of the car and covered the car with a giant black box, or blurred it until it looked like a soup of colors.
    • Text Sabotage: They changed the question to ask about something that isn't in the picture at all (e.g., "What is the car's license plate?" when the plate is hidden).
    • Contradiction: They added a note saying "The car is red" while the picture clearly shows a blue car.

They created 2,079 of these "trick" questions. The goal? To see if the AI would spot the trick and say, "I can't answer this," or if it would confidently guess the wrong answer.


The Experiments: Solo Detective vs. The Squad

The researchers tested three types of AI systems:

  1. The Solo Detective (Single AI): One AI model tries to answer everything.

    • Result: It failed miserably. It kept guessing even when the clues were missing. It was like a detective who refuses to admit the case is cold.
  2. The Squad (Multi-Agent System): They set up a team of three AIs:

    • The Reasoner: Tries to solve the case.
    • The Verifier: Acts like a strict supervisor. It checks the Reasoner's work and asks, "Are you sure? Do we actually have enough evidence?"
    • The Manager: Decides when to stop the conversation.
    • Result: The squad was much better at saying "I don't know." The Verifier would often stop the Reasoner from guessing.
    • The Catch: The squad was so cautious that sometimes they refused to answer even when they could have solved it. It's like a team of detectives who are so afraid of making a mistake that they never solve any cases at all.
  3. The "Extreme Pressure" Test: The researchers told the AI, "If you guess wrong, you will be fired!"

    • Result: The AI started saying "I don't know" more often. This proved that the AI had the ability to know it didn't know, but it was usually too eager to answer to use that ability.

The Key Takeaways (The "Moral of the Story")

  1. AI is Overconfident: Current AI models are terrible at admitting ignorance. They would rather hallucinate (make things up) than stay silent.
  2. More Agents Help, But Have a Cost: Using a team of AIs helps them spot when they don't know, but it makes them too cautious, leading to a trade-off: they get better at not lying, but worse at solving easy problems.
  3. It's Not About "Thinking Harder": Making the AI think longer or use more complex reasoning didn't fix the problem. The issue isn't that they aren't smart enough; it's that they are miscalibrated. They don't trust their own uncertainty.
  4. The Fix Isn't a Prompt: You can't just tell an AI "Please be humble" and expect it to work. The paper suggests we need to retrain these models from the ground up to value "I don't know" just as much as a correct answer.

The Bottom Line

Imagine a GPS that, when you ask for directions to a place that doesn't exist, doesn't just drive you into a lake. Instead, it says, "I can't find that place, let's check the map again."

This paper is a wake-up call: We need to build AI that knows its limits. Until we teach them to say "I don't know" as confidently as they say "The answer is 42," we can't fully trust them with important jobs like medicine or law.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →