← Latest papers
💬 NLP

Why Don't You Know? Evaluating the Impact of Uncertainty Sources on Uncertainty Quantification in LLMs

This paper introduces a new dataset to systematically evaluate how different sources of uncertainty—such as knowledge gaps, output variability, and input ambiguity—affect the performance of existing uncertainty quantification methods in Large Language Models, revealing that many methods fail or become misleading when uncertainty arises from factors beyond mere knowledge limitations.

Original authors: Maiya Goloburda, Roman Vashurin, Fedor Chernogorsky, Nurkhan Laiyk, Daniil Orel, Preslav Nakov, Maxim Panov

Published 2026-04-14
📖 4 min read☕ Coffee break read

Original authors: Maiya Goloburda, Roman Vashurin, Fedor Chernogorsky, Nurkhan Laiyk, Daniil Orel, Preslav Nakov, Maxim Panov

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

Imagine you are hiring a very smart, well-read but slightly overconfident robot assistant to help you with important tasks. You ask it questions, and it answers instantly. But sometimes, the robot is wrong. The big question for developers is: How do we know when the robot is guessing versus when it's actually sure?

This paper is like a detective story investigating how well we can tell the difference between the robot's different types of "doubt."

The Problem: One Size Doesn't Fit All

Currently, most systems try to give the robot a single "confidence score" (like a percentage from 0% to 100%) to say how sure it is. The paper argues this is like trying to describe a storm, a traffic jam, and a flat tire all with the same word: "Problem."

The authors realized that a robot's uncertainty comes from three very different sources, and treating them the same way causes confusion:

  1. The "I Don't Know" Gap (Model Knowledge):

    • The Analogy: You ask the robot, "Who was the 45th President of the US?" but the robot was trained on data that stops before that happened. It genuinely doesn't know the answer.
    • The Right Move: The robot should say, "I don't know," or ask you to check a book.
  2. The "Pick Your Favorite" Scenario (Output Variability):

    • The Analogy: You ask, "Name a fruit that is red." The robot could say "Apple," "Strawberry," or "Cherry." All are correct. If the robot says "Apple" with 100% confidence, it's not lying; it just picked one valid option from a list.
    • The Right Move: The robot should feel confident, even though there are many right answers. It shouldn't panic just because there are options.
  3. The "Vague Question" Trap (Input Ambiguity):

    • The Analogy: You ask, "Who won the game?" but you never told the robot which game. The robot has to guess if you mean soccer, chess, or a video game.
    • The Right Move: The robot should stop and ask, "Which game do you mean?" instead of confidently guessing "The Lakers" and being wrong.

The Experiment: Building a Special Test

To figure out which "confidence meter" works best for which situation, the authors built a special test dataset. Think of it like a driving test with three specific tracks:

  • Track A: A road with a missing bridge (Knowledge Gap).
  • Track B: A road with three valid exits (Output Variability).
  • Track C: A road with no signs (Ambiguity).

They tested many different "confidence meters" (mathematical methods) on these tracks to see which one could correctly identify the problem.

The Big Discovery

The results were surprising and a bit worrying:

  • The "Knowledge Gap" Meter works great: When the robot genuinely doesn't know something, most confidence meters correctly say, "Hey, I'm unsure here."
  • The "Vague Question" Meter fails: When the question is unclear, the robot often confidently guesses an answer anyway. The confidence meters think the robot is sure, even though it's actually guessing in the dark.
  • The "Pick Your Favorite" Meter gets confused: When there are multiple right answers, some meters think the robot is "uncertain" just because it didn't pick the exact same word every time, even though the answer was correct.

The Metaphor: It's like having a smoke detector that works perfectly when there's a fire, but starts screaming when you just open a window (variability) or when you walk into a foggy room (ambiguity). You end up ignoring the alarm because it's always going off for the wrong reasons.

Why This Matters

If we use these flawed confidence meters in real life, bad things could happen:

  • In Medicine: A robot might confidently give a wrong diagnosis because the patient's symptoms were vague, and the robot didn't ask for clarification.
  • In Law: A robot might refuse to answer a simple question because it thinks there are "too many possible answers," slowing down the work.

The Conclusion

The paper concludes that we need to stop using a single "confidence score." Instead, we need smart, multi-tool systems that can ask:

  • "Do you not know the answer?" (Check knowledge)
  • "Is the question unclear?" (Check ambiguity)
  • "Are there many right answers?" (Check variability)

Only by understanding why the robot is uncertain can we teach it to behave safely: admitting ignorance when it doesn't know, asking for clarity when the question is vague, and staying confident when it's just picking from a list of correct options.

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 →