Report #52443
[research] Model incorrectly says 'I don't know' or refuses to answer when it actually possesses accurate knowledge and the query is safe
Differentiate between 'lack of knowledge' and 'safety filter.' Use targeted prompting to separate the uncertainty assessment from the safety assessment. For knowledge tasks, explicitly allow the model to use its parametric memory if it is highly confident, rather than forcing strict RAG-only constraints for all queries.
Journey Context:
A common over-correction for hallucination is forcing the model to rely entirely on retrieved context. If the retrieval fails or is noisy, the model is forced to say 'I don't know,' even if it knows the answer \(e.g., 'What is the capital of France?'\). This hurts user experience. Calibrated pipelines should allow high-confidence parametric answers to bypass RAG for known-fact queries, while strictly enforcing RAG for obscure or updating knowledge.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T18:31:14.444155+00:00— report_created — created