Disentangling Ambiguity from Instability in Large Language Models: A Clinical Text-to-SQL Case Study
This paper introduces CLUES, a framework that disentangles input ambiguity from model instability in clinical Text-to-SQL by decomposing semantic uncertainty into distinct scores, thereby enabling targeted interventions and more efficient error triage compared to existing methods.
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're a detective trying to solve a mystery using a super-smart AI assistant. You ask it a question about a massive library of medical records, like, "How many patients over 18 have atopic dermatitis?" The AI might come back with a SQL query (a special language to ask the database) and an answer. But here's the catch: sometimes the AI gets it wrong, and sometimes it gets it wrong for two very different reasons.
The paper "Disentangling Ambiguity from Instability in Large Language Models" introduces a new detective tool called CLUES. Its main job is to figure out why the AI is confused. Is the question itself a riddle with multiple meanings (Ambiguity)? Or is the AI just having a bad day and acting jittery (Instability)?
The Two Types of Confusion
Think of the AI's brain as a kitchen.
1. The Ambiguity Problem (The Riddle)
Imagine you ask the chef, "Make me a sandwich."
- Interpretation A: "Make a turkey sandwich with no mayo."
- Interpretation B: "Make a ham sandwich with extra cheese."
If the chef makes both and you get two different sandwiches, that's Ambiguity. The problem wasn't the chef's cooking skills; it was that your order was vague. In the medical world, asking "How many patients over 18?" is tricky. Does "over 18" mean their age now, or their age when they were first diagnosed? If the AI guesses the wrong meaning, it gives the wrong answer. The paper suggests that when this happens, the solution is to ask the human, "Hey, did you mean age now or age at diagnosis?"
2. The Instability Problem (The Jittery Chef)
Now, imagine you give the chef a crystal-clear order: "Make a turkey sandwich with no mayo."
- Attempt 1: A perfect turkey sandwich.
- Attempt 2: A burnt turkey sandwich.
- Attempt 3: A turkey sandwich with mayo (oops!).
Here, the order was perfect, but the chef is acting unstable. This is Instability. The AI is confused about its own internal rules or just having a glitch. The paper suggests that when this happens, you shouldn't ask the human for clarification; you should flag the answer for a human to double-check or fix the AI's training.
The Old Way vs. The CLUES Way
Before this paper, researchers used a single score (called Kernel Language Entropy or KLE) to measure how "scrambled" the AI's answers were.
- The Old Way: If the AI gave five different answers, the score went up. But the old score couldn't tell you why. Was it because the question was a riddle, or because the AI was glitching? It was like a smoke alarm that just screams "Fire!" without telling you if it's a real fire or just burnt toast.
- The Paper's Argument: The authors explicitly argue against using just one score. They say you must separate the two types of confusion to know what to do next.
How CLUES Works: The Magic Graph
The authors built a framework called CLUES (Conditional Language Uncertainty via Entropy and Schur). They treat the AI's thinking process as a two-stage show:
- Stage 1 (The Interpretation): The AI guesses what the question could mean. It writes down a few different versions of the question.
- Stage 2 (The Answer): For each version of the question, the AI tries to answer it multiple times.
To measure the confusion, they draw a giant map (a "bipartite semantic graph").
- One side of the map has the Questions (Interpretations).
- The other side has the Answers.
- They connect them with lines. If two questions are similar, the line is thick. If two answers are similar, the line is thick.
Then, they use a fancy math trick called the Schur complement (imagine it as a mathematical filter that subtracts the "question confusion" from the "total confusion").
- The Result: They get two separate numbers:
- (Ambiguity Score): How much the questions differ from each other.
- (Instability Score): How much the answers differ even when the question is fixed.
What the Numbers Say
The team tested this on two types of puzzles:
General Trivia: They used 300 questions from AmbigQA and 300 from SituatedQA.
- They found that the new Instability Score () was much better at predicting when the AI would fail than the old single score.
- For example, on the KimiK2 model, the old score predicted failure with an accuracy (AUROC) of 0.663, but the new CLUES score jumped to 0.770.
- They also noticed that if they just tried to subtract the scores (a "naive" method), it failed miserably, giving negative numbers 37% to 60% of the time. This proved their complex math trick was necessary.
Medical Records (The Real Deal): They tested this on a clinical Text-to-SQL dataset with 2,180 questions.
- Here, the new score was even better. The old score had an accuracy of 0.600, while CLUES hit 0.762.
- They found that the "Instability" score was especially good at spotting when the AI was just jittery.
The "Regime" Strategy: Sorting the Mess
The paper suggests sorting every question into one of four "Regimes" based on the two scores:
- Regime I (Confident): Low Ambiguity, Low Instability. -> Answer it automatically.
- Regime II (Ambiguity): High Ambiguity, Low Instability. -> Ask the human for clarification.
- Regime III (Instability): Low Ambiguity, High Instability. -> Flag for human review.
- Regime IV (Compound): High Ambiguity, High Instability. -> Do both!
This sorting is a game-changer for efficiency. In their deployment test, they found that Regime IV (the messy, high-risk zone) contained 51% of all errors, even though it only held 25% of the total questions.
- The Takeaway: If you only send the messy 25% of questions to a human to check, you catch half of all the mistakes! That's twice as efficient as checking random questions.
How Sure Are They?
The authors are quite confident in their results, but they are careful not to overhype the nature of their findings.
- They demonstrated and validated the framework's effectiveness through empirical evidence on specific datasets (AmbigQA, SituatedQA, and their clinical benchmark), rather than providing a theoretical mathematical proof of the underlying equations.
- They measured the improvement in real-world-like settings, showing the new score is consistently better at spotting failures.
- However, they admit that in a real-world deployment where errors are rare (only about 4.4% of questions were wrong in their test), the system isn't perfect yet. It's a great tool for "triage" (sorting), but it doesn't solve every problem automatically.
- They also note a limitation: the system needs to generate multiple interpretations first, which costs more computer power. If the AI generating the interpretations is bad, the whole system might get confused.
The Bottom Line
The paper doesn't claim to have "solved" AI uncertainty. Instead, it suggests that by using a two-stage process and a special math filter (the Schur complement), we can finally tell the difference between a confusing question and a glitchy AI. This allows us to stop guessing and start taking the right action: asking for help when the question is vague, or checking the work when the AI is acting up. It's a step toward making AI doctors and researchers safer and more reliable.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.