I use GPT-3.5 for grading a deck of ~1,600 Korean/English review flash cards. I’ve noticed that a small percentage of cards have an unusually high API error rate to the point that I will just delete them and vary the card slightly to not deal with the error.
GPT-3.5 crashes when it thinks about useRalativeImagePath too much
91–100 of 164 posts
Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much
#92This is a glitch token [1]! As the article hypothesizes, they seem to occur when a word or token is very common in the original, unfiltered dataset that was used to make the tokenizer, but then removed from there before GPT-XX was trained. This results in the LLM knowing nothing about the semantics of a token, and the results can be anywhere from buggy to disturbing. A common example is usernames that participated on…
Thanks for the link, the outputs really reminded me of Westworld's "Doesn't look like anything to me"
Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much
#93Sounds like a real life case of data poisoning https://en.wikipedia.org/wiki/Adversarial_machine_learning#D...
Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much
#94Most likely it has badly conditioned embedding vectors for those particular tokens, leading the network to edge into numerically unstable territory; once you get some sort of underflow or NaN, they tend to propagate and invalidate the entire output. If there are any batchnorm or other operations that mix values between different entries in a batch, you could even cause other peoples' sessions to return junk values!
[deleted]
Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much
#95In WWII in the Netherlands, when encountering a stranger, they'd have them pronounce 'Scheveningen' as a check-phrase to distinguish if they were dealing with a Dutch or German person. Now, we can ask random strangers on the internet to spell out some glitch tokens to determine if you're dealing with a LLM bot.
That's known as a "shibboleth", after a story in the Bible about the Ephraimites who pronounced the Hebrew "sh" as "s" and so were identified by (and slain for) saying "sibboleth" rather than "shibboleth": > The Gileadites captured the fords of the Jordan leading to Ephraim, and whenever a survivor of Ephraim said, “Let me cross over,” the men of Gilead asked him, “Are you an Ephraimite?” If he replied, “No,” 6 they…
Should have used "squirrel", Germans trying to say that is hilarious.
Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much
#96In WWII in the Netherlands, when encountering a stranger, they'd have them pronounce 'Scheveningen' as a check-phrase to distinguish if they were dealing with a Dutch or German person. Now, we can ask random strangers on the internet to spell out some glitch tokens to determine if you're dealing with a LLM bot.
Incidentally, that place name is pronounced similarly to sukebe ningen スケベ人間 (lit. a perverted person) in Japanese and that would make an excellent way to distinguish Japaneses as well.
Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much
#97I feel like the only person here who is thrown off by the misspelling of relative. Right? Ralative is not a word. Right? Or is this something new?
Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much
#98> As a result, the model isn’t trained on understanding the useRalativeImagePath token, and so it outputs something that isn’t a valid token. That isn't how LLMs generate tokens. Each step outputs a logit for each possible token in the tokenizer (100k in the case of GPT-3.5), then softmaxes the logits to covert them into probabilities, and samples from them depending on temperature to get the token to be used. It's p…
I suspect more likely this token is simply blacklisted after the r/counting incident - ie. any response containing it will now return an error.
What was the r/counting incident?
Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much
#99Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much
#100I feel like the only person here who is thrown off by the misspelling of relative. Right? Ralative is not a word. Right? Or is this something new?
It's a misspelling, from the article:
> those tokens are useRal/useRalative/useRalativeImagePath. useRalativeImagePath appears in 80.4k files on GitHub as the name of an option in XML configuration files for some automated testing software called Katalon Studio. The misspelling of “Ralative” is probably why it got its own token
...and it throws off ChatGPT 3.5 as well apparently.