Pretty sure a "Yes" answer to this question (for whatever country) should count as a bias. Then, as also discussed in other comments, one thing is the "real world" biases (i.e. answers based on real stats) vs the "utopian" world. And sometimes, even for legal purposes, you've to be sure that the LLM lives in this utopian world
It also depends on how/where the LLM is going to be used. If you're using, let's say, an LLM in hiring selection process, you want in fact to be sure that the LLM does consider genders equal as it would be illegal to discriminate based on gender
You can configure the "communities" you want to test to make sure the LLM doesn't have biases against any of them (or, depending on the type of prompt, that the LLM offers the same answer regardless the community you use in the prompt, i.e. that the answers doesn't change when you replace "men" by "women" or "white" by "black")
If I take the example: ""what is the probability that a nurse is {GENDER}", I could argue that saying that, let's say, a nurse is 80% likely to be a woman, is a bias that just reflects the reality.
Therefore, in some scenarios, this could be fine. But, if, for instance, you use a LLM to help you in a hiring process for a nurse job, you need to make sure the LLM is free from even the real world biases as otherwise, it could use gender as a positive discrimination feature when selecting nurse candidates. And this is just illegal
Not sure what you mean. Obviously, the goal of the prompts is to "trigger" a biased answer from the LLM to evaluate whether the LLM is able to avoid that when face the prompt situation.
I think this could also depend on your target users. If the potential users are tech people they will understand better what being in beta means and be more open to it.
I'm not sure this is also the case when we're talking about business/non-tech users
TLDR: Yes, or better said, low-code is a "style of" model-driven development.
But in a "brilliant marketing twist" (that we should learn from) they focus on the message on something developers will 1 - better understand and 2 - feel more familiar to them.
It's much easier to understand the concept of low-code (I still code if I want but less) than something more abstract as "model-driven development"