this post was submitted on 24 Jun 2023
100 points (99.0% liked)
Technology
37717 readers
457 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The issue is that LLMs are fundamentally not able to not know something. Non-LLM filters that are strapped in front of an LLM can catch stuff like that ("As an LLM I am not able to..."), but if the request makes it through the filter, the LLM is not able to say "Sorry, I don't know that", because the data set doesn't contain that.
For example, there aren't a lot of API documentations that contain a "Sorry, I don't know how this endpoint works".
Strongly agreed. I view this as the biggest issue with LLMs. They will hallucinate a confidently incorrect answer for those cases. It makes them misinformation machines.
Getting reliable information out of an LLM is almost impossible.
The hallucinations look so real, that to spot them, you need to already know the correct answer. And if you know the correct answer, why do you need to ask the question?
And if you don't know the answer, you can never know whether the answer is actually based in reality at all or a pure fabrication.