Large language model AIs might seem smart on a surface level but they struggle to actually understand the real world and model it accurately, a new study finds.
Large language model AIs might seem smart on a surface level but they struggle to actually understand the real world and model it accurately, a new study finds.
An important characteristic of a model is “stability.” Stability means that small changes in input produce small changes in output.
Stability is important for predictability. For instance, suppose you want to make a customer support portal. You add a bot hoping that it will guide the user to the desired workflow. You test the bot by asking it a bunch of variations of questions, probably with some RLHF. But then when it goes to production, people will start asking it variations of questions that you didn’t test (guaranteed). What you want ideally, is that it will map the variants to the best workflow that matches what the customer wants. Second best would be to say “I don’t know.” But what we have are bots who will just generate some crazy off-the-wall crap, and no way to prevent it.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
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.
An important characteristic of a model is “stability.” Stability means that small changes in input produce small changes in output.
Stability is important for predictability. For instance, suppose you want to make a customer support portal. You add a bot hoping that it will guide the user to the desired workflow. You test the bot by asking it a bunch of variations of questions, probably with some RLHF. But then when it goes to production, people will start asking it variations of questions that you didn’t test (guaranteed). What you want ideally, is that it will map the variants to the best workflow that matches what the customer wants. Second best would be to say “I don’t know.” But what we have are bots who will just generate some crazy off-the-wall crap, and no way to prevent it.