English

SelfReflect: Can LLMs Communicate Their Internal Answer Distribution?

Computation and Language 2026-02-06 v4 Artificial Intelligence Machine Learning Machine Learning

Abstract

The common approach to communicate a large language model's (LLM) uncertainty is to add a percentage number or a hedging word to its response. But is this all we can do? Instead of generating a single answer and then hedging it, an LLM that is fully transparent to the user needs to be able to reflect on its internal belief distribution and output a summary of all options it deems possible, and how likely they are. To test whether LLMs possess this capability, we develop the SelfReflect metric, an information-theoretic distance between a given summary and a distribution over answers. In interventional and human studies, we find that SelfReflect indicates even slight deviations, yielding a fine measure of faithfulness between a summary string and an LLM's actual internal distribution over answers. With SelfReflect, we make a resounding negative observation: modern LLMs are, across the board, incapable of revealing what they are uncertain about, neither through reasoning, nor chains-of-thoughts, nor explicit finetuning. However, we do find that LLMs are able to generate faithful summaries of their uncertainties if we help them by sampling multiple outputs and feeding them back into the context. This simple approach shines a light at the universal way of communicating LLM uncertainties whose future development the SelfReflect score enables. To support the development of this universal form of LLM uncertainties, we publish the code that implements our metric for arbitrary LLMs under https://github.com/apple/ml-selfreflect .

Keywords

Cite

@article{arxiv.2505.20295,
  title  = {SelfReflect: Can LLMs Communicate Their Internal Answer Distribution?},
  author = {Michael Kirchhof and Luca Füger and Adam Goliński and Eeshan Gunesh Dhekane and Arno Blaas and Seong Joon Oh and Sinead Williamson},
  journal= {arXiv preprint arXiv:2505.20295},
  year   = {2026}
}

Comments

Accepted at ICLR 2026

R2 v1 2026-07-01T02:40:36.681Z