this post was submitted on 27 Feb 2024
58 points (100.0% liked)

Technology

37718 readers
510 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
 

Abstract:

Hallucination has been widely recognized to be a significant drawback for large language models (LLMs). There have been many works that attempt to reduce the extent of hallucination. These efforts have mostly been empirical so far, which cannot answer the fundamental question whether it can be completely eliminated. In this paper, we formalize the problem and show that it is impossible to eliminate hallucination in LLMs. Specifically, we define a formal world where hallucina- tion is defined as inconsistencies between a computable LLM and a computable ground truth function. By employing results from learning theory, we show that LLMs cannot learn all of the computable functions and will therefore always hal- lucinate. Since the formal world is a part of the real world which is much more complicated, hallucinations are also inevitable for real world LLMs. Furthermore, for real world LLMs constrained by provable time complexity, we describe the hallucination-prone tasks and empirically validate our claims. Finally, using the formal world framework, we discuss the possible mechanisms and efficacies of existing hallucination mitigators as well as the practical implications on the safe deployment of LLMs.

you are viewing a single comment's thread
view the rest of the comments
[–] Daxtron2@startrek.website 5 points 8 months ago (1 children)

Just want to point out that you shouldn't use them as a single point of truth. They can and do give factual information, but just as with every source, you should verify and know what you're actually doing with the output. Part of why it's so useful to me as a programmer is that I can determine between good and bad outputs and utilize the good ones.

[–] eldrichhydralisk@lemmy.sdf.org 4 points 8 months ago (1 children)

Which is exactly what the paper recommends! As long as you have something that isn't an LLM in the pipeline to vet the output and you're aware is the tech's limitations, they can be useful tools. But some of those limitations might be a more solid barrier than some sales departments would like us to believe.

[–] Daxtron2@startrek.website 1 points 8 months ago

Yep! Figured id share for the 90% who won't read it though haha. Sales teams truly are the worst when it comes to that