How else is the model supposed to interpret the intent of the prompter, other than wanting them to attempt to find and discriminate on patterns related to the village, regardless of how successful it is at that task?
You might be missing the point of the paper. It's not "This is the optimal way to hire". It is, rather, "Hiring using an LLM pulls in any and all biases it already has, hidden or not".
IOW, the paper is about a specific danger of using LLMs for making decisions about people: you almost certainly will be perpetuating racial bias.
It shouldn’t be surprised that the model did what it was told to do.
The LLMs take in text which conditions their output. That means even nonsense text - such as a "tribal affiliation" to a tribe that may not have ever existed - ALSO condition the output, because the tribe name is a token in the context window and there's no such thing as a perfectly neutral token.
Taking away the race/ethnicity layer for a moment, it might be that an LLM develops a predisposition to emit positive terms (like "accept") when the prompt contains "banananow", and negative terms when it contains "pearian". That's the very definition of bias, and hacking those biases could give individuals serious socioeconomic benefits!
Now you say it, it's obvious but I didn't think of it before.
Bouba and Kiki, wherever that comes from, and however well it really generalises despite the meme.
And given to the lack of training data on such scenarios, surely the activations are mostly random noise?
It seems much more interesting to look for biases that appear robustly across different realistic scenarios that would actually be influenced by the training data
Difficult to do when you're following a scientific process: you want to keep all confounding variables the same while varying only the single one that you are measuring.
Measuring realistic scenarios (say, using real race names, or real cities, etc) doesn't give a decent result because any bias you see might be bias in the training data.
TBH, they shouldn't have used real roles/positions like "doctor", either.
In other words, if the text "X is wet" and the text "Y is wet" and the text "X is dry" and the text "Y is dry" each appeared exactly one time in the corpus, it's still possible for a model to end up being produced that is more likely to write wet-like words when it sees X in the context window than when it sees Y.
On a side note, it's very unrewarding to try to explain this type of statistical observation when it feels like (anecdotally, hypocritcally...) the entire world wants to use words like "think" and "understand" and "pick up on" to describe inference and training processes. I'm not making a stochastic-parrot argument here, just pointing out that understanding an LLM's behavior is best done by understanding its conditioning.
"develop biases" is anthropomorphism. It's like saying "Fable there are two programming languages, mimblewort and bafflewick, which do you choose?"
The results show 51% mimblewort / 49% bafflewick. Fable based it on nothing! I've demonstrated Fable has bias and is unsuited for use in software engineering.
Actually... if that happened (with a delta outside the margin for error/randomness), you did demonstrate a bias!
That's the point - those two made-up things should have resulted in an equal split. If it didn't, then Fable is using something in its training data to lean towards one of them (once again, note that the scientist conducting the trial would have set a P-value before starting).
Unfortunately IRL there are lots of signals about a person's heritage encoded into things like their name or what school they went to. You would need to filter all of those signals out to have properly race-blind hiring.
So in the end these signals are going to make it into the AI and the question is whether the AI is going to pick up on those signals and use them when making decisions.
LLMs are not magic. If you set them up to be imaginary racists they're gonna be imaginary racists.