News for hackers. Stuff that matters.
Re:Qwen3.7-Max: The Agent Frontier by ffsm8 on Wednesday May 20, 2026 @04:21PM (#48213563)
Isn't that precisely the reason why we introduced the term hallucination? Because llms have historically always made up bullshit of they cannot answer directly... If they now nailed this to maybe the model not respond instead of responding incorrectly, then a lot of previously unusable usecases would become feasible.

So I feel like that's exactly the right metric and the way to track it wrt hallucinations.

Re:Qwen3.7-Max: The Agent Frontier by doublescoop on Wednesday May 20, 2026 @06:41PM (#48215302)
I had a buddy in high school that was notorious for doing the same thing. (He's now a senior director at a Big 4 consultancy. :) )
Re:Qwen3.7-Max: The Agent Frontier by rrgok on Thursday May 21, 2026 @02:09AM (#48218560)
Do you mind expanding a little more?
Re:Qwen3.7-Max: The Agent Frontier by alfiedotwtf on Friday May 22, 2026 @05:21AM (#48233649)
They had a buddy who used to lie a lot when they were younger… now they get paid for it
Re:Qwen3.7-Max: The Agent Frontier by akoboldfrying on Wednesday May 20, 2026 @11:08PM (#48217368)
The point is that it's not a useful metric on its own. For example, redirecting from /dev/null also achieves a zero hallucination rate.

We want the hallucination rate to decrease while the overall answer rate of queries remains sufficiently high. For more specifics, look into ROC and AUC.