← Latest papers
🤖 machine learning

LLMs Should Express Uncertainty Explicitly

This paper argues that large language models should be trained to explicitly express uncertainty through two complementary interfaces—global verbalized confidence for calibrating final answers and local reasoning-time signaling for triggering interventions—to optimize decision-making in tasks like retrieval and verification.

Original authors: Junyu Guo, Shangding Gu, Ming Jin, Costas Spanos, Javad Lavaei

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

Original authors: Junyu Guo, Shangding Gu, Ming Jin, Costas Spanos, Javad Lavaei

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, but slightly overconfident, research assistant named "LLM" to answer your questions. Sometimes, LLM knows the answer perfectly. Other times, it's guessing, but it doesn't realize it's guessing. It just confidently says, "The answer is X!" even when it's wrong. This is dangerous because if you trust a confident lie, you might make a bad decision.

This paper proposes a new way to train LLMs so they can honestly admit when they are unsure. The authors argue that instead of just guessing, the model should have two different "tools" to tell you when it's in trouble, depending on when the trouble happens.

Here is the breakdown using simple analogies:

The Two Tools: The "Confidence Score" vs. The "Red Flag"

The paper compares two ways to make the model express uncertainty. Think of them as two different safety mechanisms in a car.

1. The Global Interface: The "Speedometer" (Verbalized Confidence)

How it works: After the model finishes its answer, it gives you a number, like "I am 90% sure this is correct" or "I am only 20% sure."
The Analogy: Imagine a weather forecaster. Instead of just saying "It will rain," they say, "There is a 90% chance of rain."
What the paper found:

  • The Problem: Before training, the model was like a weather forecaster who always says "100% chance of rain," even when it's sunny. This is called being "overconfident."
  • The Fix: The authors trained the model to be honest about its "speedometer."
  • The Result: The model stopped lying about its confidence. If it was wrong, it now said, "I'm only 30% sure." This didn't make the model smarter at finding the right answer, but it made it much better at telling you when to trust it.
  • Best Use: Use this when you need to decide, "Should I trust this final answer or not?"

2. The Local Interface: The "Check Engine Light" (The <uncertain> Token)

How it works: Instead of waiting until the end, the model is trained to stop in the middle of its thinking process and shout a specific code word: <uncertain>.
The Analogy: Imagine a mechanic working on your car. Instead of waiting until the car breaks down to tell you something is wrong, they stop mid-repair, hold up a red flag, and say, "Whoa, I'm stuck here. I don't know how to fix this part. I need to call a senior mechanic for help."
What the paper found:

  • The Problem: Before training, when the model got stuck on a hard fact, it would just keep guessing silently until it gave a wrong answer.
  • The Fix: The model learned to raise a "Red Flag" the moment it hit a wall in its reasoning.
  • The Result: This acts as an early warning system. It catches mistakes while they are happening. This allows a computer system to pause the model, go look up the answer in a database (retrieval), and then let the model finish.
  • Best Use: Use this when you want to catch mistakes early so you can fix them before the model finishes its sentence.

Why This Matters: The "Silent Failure" vs. The "Honest Mistake"

The authors discovered a crucial difference between the two methods:

  • Before training: The model made "Silent Failures." It would confidently say the wrong thing. You wouldn't know it was wrong until it was too late.
  • After training:
    • The Speedometer method turned "Silent Failures" into "Honest Mistakes." The model still got the answer wrong, but it said, "I'm not sure," so you knew not to trust it.
    • The Red Flag method turned "Silent Failures" into "Intervention Points." The model stopped itself and asked for help, preventing the mistake from ever becoming a final answer.

The Secret Sauce: How the Model Learned

The paper also looked under the hood to see how the model learned this.

  • The Speedometer (Global): The model didn't need to change its brain much. It just learned to read its own internal "uncertainty meter" more accurately and report it honestly. It's like teaching a person to read their own pulse correctly.
  • The Red Flag (Local): This required a deeper change. The model had to reorganize how it thinks. It learned to build a specific "panic button" into its reasoning process. It's like teaching a person to physically stop and raise their hand when they feel lost, rather than just feeling lost internally.

The Big Takeaway

The paper concludes that uncertainty isn't just one thing. To make AI truly useful and safe, we need to teach it two different skills:

  1. Global Confidence: To tell us, "Hey, I'm not sure about this final answer, so don't trust it blindly."
  2. Local Signaling: To tell us, "I'm stuck right here in the middle of my thought process; please go get more information for me."

By giving AI these two ways to say "I don't know," we can stop it from confidently hallucinating (making things up) and start using it as a tool that knows its own limits.

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 →