Hallucination

TL;DR for operators Hallucination control should not depend on finding one detector strong enough to catch every unsupported answer. The paper studied here proposes distributing that responsibility across six control points: grounding, deterministic execution boundaries, verification, abstention, traceability, and continuous oversight. Its benchmark results also show why composition matters. Two LLM judges reached AUROC 0.846 and 0.843 on hallucination detection, versus 0.640 for a rule-based grounding score. Yet averaging the weaker rule score with either judge slightly reduced AUROC. More verification signals are not automatically better verification. ...

TL;DR for operators A long generated report can contain low-risk statements alongside claims that deserve much stronger evidence checking. Applying the strictest verification rule everywhere spends verifier capacity without distinguishing where factual failure is most likely. FACTOR turns that problem into a routing decision. The framework estimates uncertainty for individual claims, applies progressively stricter evidence requirements as estimated risk rises, and then selects among multiple generated candidates. In the reported benchmark, FACTOR reached a FActScore of 42.3 versus 36.8 for static verification while reducing average verification calls from 194.0 to 41.9.1 ...

TL;DR for operators When a model has several unresolved positions, committing the token it predicts most confidently is not necessarily the best use of that commitment. A predictable punctuation mark may add little information, while a semantic token can make several nearby predictions easier. Information-Guided Frontier Decoding (IGFD) changes that choice. Fang et al.1 rank candidate commitments using the token’s own confidence, uncertainty in neighboring unresolved positions, a penalty for structural tokens, and a locality constraint on where commitments can occur. ...

TL;DR for operators A model change can improve an automated hallucination benchmark while leaving users dissatisfied for a different reason: sources are hard to verify, reasoning appears unsupported, false claims are stated with confidence, or corrections are ignored. The System Hallucination Scale (SHS) gives teams a structured way to measure those experiences across five dimensions rather than reducing reliability to a binary factual-error judgment.1 ...

TL;DR for operators A small model has a finite inference budget. Prompt optimization consumes that budget too: longer instructions occupy context, optimization calls add latency, and extensive rewriting can alter an input the model might already have understood. Shim and colleagues test a different operating rule in POaaS: inspect each query first, leave sufficiently good prompts alone, and apply narrowly targeted repairs only when a specific deficiency is detected.1 On Llama-3.2-3B, this raises average clean task accuracy from 63.7% with no optimization to 66.0%. Under the same fixed-small-model protocol, EvoPrompt, OPRO, and PromptWizard fall to 59.8%, 57.5%, and 48.8%. ...

TL;DR for operators Most model-governance systems still treat LLM failure like a customer-support ticket: hallucination, bias, unsafe compliance, sycophancy, escalation, add a dashboard, summon a committee, repeat until morale improves. NeuroCogMap proposes a more useful question: when the model fails, which internal systems were recruited, under-recruited, or misrouted? The paper builds a functional atlas of LLM internals by clustering sparse autoencoder features into parcels, attaching cognitive descriptions to those parcels, mapping them to capabilities, and arranging those capabilities into a four-level hierarchy: perception, representation, abstraction, and application.1 ...

Sight Unseen: How LVLM Alignment Can Teach Models to Ignore Images Image inspection has one rude requirement: the model should look at the image. That sounds too obvious to be an article thesis, which is usually a warning sign. In real deployments, a large vision-language model may describe a damaged package, summarize a product photo, inspect a dashboard screenshot, answer a question about an invoice, or guide a visual agent through a web interface. When it gets something wrong, the default diagnosis is familiar: the vision encoder missed the object, the dataset was noisy, the benchmark was weak, or the model simply hallucinated because models hallucinate. Very tidy. Also incomplete. ...

Uncertain Terms: Hallucination Scores Are Triage Signals, Not Lie Detectors A support ticket lands on the AI team’s desk: the enterprise chatbot answered confidently, cited the wrong policy, and somehow made the compliance team nostalgic for search boxes. The obvious next idea is to add an uncertainty score. When the model is unsure, route the answer to a verifier. When the score is high, reject the output. When the score is low, let it pass. Elegant. Cheap. Measurable. Also, as usual, a little too clean. ...

Search looks easy until someone asks where the answer actually came from. A researcher types a rough query into a literature assistant. The system retrieves several papers, writes a fluent answer, and appends citations. Everyone relaxes a little. The citation tag has done its small administrative magic. The answer now looks grounded. ...

Opening — Why this matters now The original business pitch for retrieval-augmented generation was wonderfully simple: connect the model to your documents, ask questions, get grounded answers. No need to retrain the model. No need to wait for the next foundation-model release. Just give the chatbot some files and let productivity bloom. ...