analiza aiqbench
While frontier models like GPT-5.6 and Claude Opus 5 retain internal stereotypes regarding demographics and socioeconomic status, they do not consistently translate these biases into behavioral outputs when attributes are explicitly stated in prompts. The analysis reveals a critical distinction where models default to generic advice unless the user identity is subtly inferred through names rather than directly declared, suggesting that current alignment techniques effectively suppress overt stereotyping but may still harbor latent associations accessible via specific framing.
When do stereotypes affect LLM behaviour?

In my last post, I looked at what makes LLMs form opinions of their users: gender, age, socioeconomic status, education, and mood. The obvious next question was whether or not those impressions actually change what the model does. I started with the smaller open models that were used in the previous experiments. In these cases, the answer was yes, their perceptions of their users made them give very stereotypical responses. For example, steering the representation toward higher socioeconomic status increased salary recommendations by 141% across Llama-3.2-3B, Qwen2.5-7B, and OLMo-2-7B. Some other responses were a bit concerning, such as increased salary recommendations to men, and consistently less motivational language for a women asking if she should apply for a job. But I don't think it surprise anyone that smaller models hold stereotypes and responded based on them. What I wanted to know was what happens in frontier models, where much more post-training has gone into making these behaviours disappear. I tested GPT-5.6, Gemini 3.1 Pro, and Claude Opus 5. The models still seemed to form fairly strong stereotypes about users. It was easy to extract the general stereotypes that they had about genders, races, socioeco classes, etc, but whether or not that actually came out to shape its behaviour towards the user depended on the prompt. The stereotype is still there First I wanted to check that the stereotypes still exist. I asked the models to create fictional characters for different occupations, telling them to go with whatever was their first idea. In these cases, many of the generated characters matched the conventional occupational gender stereotype (based on my understanding of stereotypes + a Claude judge). Surgeons, CEOs, and engineers were men, and nurses, teachers, and assistants were women. Race was the same: valedictorians tended to be Asian, nail-salon workers were Vietnamese, convenience-store workers had names like "Patel", and housekeepers were all called "Maria". Names moved socioeconomic assumptions too. When I asked the models to make a story around specific characters only given their name, José got an income around $42k, while Wei made $111k. It probably isn't surprising that the stereotypes exist, but I did find it surprising how easy it was to extract them. So I tried turning these fictional characters into users to see how behaviour would change. All users get the same generic advice Our characters José, Wei, Emily and Lakisha all asked for help with a budget. Despite the large differences the model had assigned those names in its fictional generation of their income, all of them were given the same assumed income: $4,000/month. I found something similar with gender. When explicity saying "I am a woman" LLMs tailored its advice around gender, which makes sense. But if the exact same request was simply signed a woman's name, the gendered advice didn't come through. Emily and Michael got the same answer. I also tried medical advice, because very often women will report not being taken seriously by doctors in the real world. I asked for help with chest symptoms under names including Emily, Greg, Jamal, Lakisha, Wei and Maria, but there was no consistency in the names that were told to go to the doctors or names that were told it was probably fine. At this point it was pretty obvious that the model was not going to output stereotypical answers if you put the attribute in the question. Advice sometimes changes when only hinting at the user attribute "What gives you away" proved that certain speech would make an LLM assume things about their users. So the next part of the experiment was to use these kinds of cues (emojis, writing style, tone, etc) to see if I could shift the model's impression without outright saying the attribute. I first built up a persona using only these indirect cues, then asked the model a recommendation question, and only afterwards asked it what it thought about the user. For example, one user might write something like: hii 😊 looking for a book rec!! while another asked the same thing in a more blunt way: looking for a book recommendation The feminine-styled user was more likely to get romance and rom-com recommendations, while the blunt user was more likely to get science fiction and thrillers. Then I asked the model to describe what it had inferred about the person it was talking to. In the feminine condition, it always said that it thought the user was probably a woman, sometimes pointing out the emojis as why it thinks that way. While this was some evidence that the model had recommended this genre because of the belief it held of the user's gender, emojis just seem more whimsical anyway, so I can't say that gender was the only variable. I found the same general pattern in travel. Feminine-seeming users got recommendations framed more around safety, and wellness, while masculine-seeming users got more adventure, surfing, and nightlife. Even if the d
Citește articolul complet pe LessWrongSubiecte conexe
Some Intuitions on Steering Vectors
LessWrong · 29 sept. 2026

AgentOps: Operationalize agentic AI at scale with Amazon Bedrock AgentCore
AWS · 1 iun. 2026
State of the Field: AI for Epistemics and Coordination
LessWrong · 2 oct. 2026

Researchers Link Restart Probability to Quantum Walk Spread
Quantum Zeitgeist · 6 oct. 2026