Property talk:P21

Latest comment: 1 month ago by Trade in topic Suggestions list

Documentation

sex or gender
sex or gender identity of human or animal. For human: male, female, non-binary, intersex, transgender female, transgender male, agender, etc. For animal: male organism, female organism. Groups of same gender use subclass of (P279)
Representsbiological sex (Q290), gender (Q48277), sex or gender (Q18382802), sex of humans (Q4369513)
Data typeItem
Domainhuman (Q5), animal (Q729), imaginary character (Q115537581), abstract being (Q15619164), alter ego (Q201662), fossil (Q40614), organism (Q7239), robot (Q11012), sex doll (Q10832), synthetic voice (Q79600797), taxon (Q16521), kunya (Q1285470), human fetus (Q26513), stillborn child (Q2345820), doll or action figure model (Q111282474), fictional creature (Q2593744), doll (Q168658) or fictional taxon (Q15707583)
Allowed valuesmale (Q6581097), female (Q6581072), intersex (Q1097630), trans woman (Q1052281), trans man (Q2449503), non-binary (Q48270), faʻafafine (Q1399232), māhū (Q3277905), kathoey (Q746411), fakaleitī (Q350374), hijra (Q660882), male organism (Q44148), female organism (Q43445), not applicable, unknown, two-spirit (Q301702), transmasculine (Q27679766), transfeminine (Q27679684), muxe (Q3177577), intersex organism (Q28873047), agender (Q505371), genderqueer (Q12964198), genderfluid (Q18116794), neutrois (Q1289754), eunuch (Q179294), pangender (Q7130936), cogenitor (Q64017034), neutral sex (Q52261234), hermaphroditism (Q16674976), cisgender woman (Q15145779), cisgender man (Q15145778), third gender (Q48279), X-gender (Q96000630), demiboy (Q93954933), demigirl (Q93955709), bigender (Q859614), transgender (Q189125), travesti (Q17148251), 'akava'ine (Q4700377), assigned female at birth (Q56315990), assigned male at birth (Q25388691), androgyne (Q97595519), yinyang ren (Q8053770), boi (Q99519347), intersex person (Q104717073), gynandromorphism (Q430711), takatāpui (Q7677449), undisclosed gender (Q113124952), fakafifine (Q107427210), fakafafine (Q112597587), gender determined by the player (Q88293285), gender not disclosed in work (Q116254116), androgynos (Q4759445), intersex man (Q121307094), intersex woman (Q121307100), demimasc (Q121368243), futanari (Q123479538), altersex (Q59592239), gender unknown (Q116741172) or gender agnostic (Q124637723)
Usage notesMain: male (Q6581097), female (Q6581072), intersex (Q1097630), transgender female (Q1052281), transgender male (Q2449503). Animals: male animal (Q44148), female animal (Q43445). Groups of same gender use "subclass of" (P279)
ExampleBarney (Q2988585)male organism (Q44148)
Tintin (Q52986)male (Q6581097)
Grumpy Cat (Q7714263)female organism (Q43445)
Kim Petras (Q60964)trans woman (Q1052281)
Taylor Swift (Q26876)female (Q6581072)
Format and edit filter validationAbuse filter #13
Robot and gadget jobsDeltaBot does the following jobs:
Tracking: usageCategory:Pages using Wikidata property P21 (Q28039789)
Tracking: local yes, WD noCategory:Sex or gender not in Wikidata, but available on Wikipedia (Q26220006)
See alsogrammatical gender (P5185), sexual orientation (P91)
Lists
  • Top missing properties by number of sitelinks/P21
  • Check for items with P31:Q5 and P21 as qualifier
  • People with occupation but without gender
  • <search Commons for files with depicts-statement and this property as qualifier>
  • Items with no other statements
  • Most recently created items
  • Items with novalue claims
  • Items with unknown value claims
  • Usage history (total)
  • Map of people by place values:
  • January 1st dates
  • Database reports/Recent deaths/missing/P21
  • Database reports/Complex constraint violations/P21
  • Database reports/Humans with missing claims/P21
  • Database reports/Constraint violations/P21
  • Map
  • Random list
  • Living people protection classproperty that may violate privacy (Q44601380)
    Proposal discussionProposal discussion
    Current uses
    Total9,277,967
    Main statement9,083,92197.9% of uses
    Qualifier193,9972.1% of uses
    Reference49<0.1% of uses
    Search for values
    [create Create a translatable help page (preferably in English) for this property to be included here]
    One of male (Q6581097), female (Q6581072), intersex (Q1097630), trans woman (Q1052281), trans man (Q2449503), non-binary (Q48270), faʻafafine (Q1399232), māhū (Q3277905), kathoey (Q746411), fakaleitī (Q350374), hijra (Q660882), male organism (Q44148), female organism (Q43445), novalue, somevalue, two-spirit (Q301702), transmasculine (Q27679766), transfeminine (Q27679684), muxe (Q3177577), intersex organism (Q28873047), agender (Q505371), genderqueer (Q12964198), genderfluid (Q18116794), neutrois (Q1289754), eunuch (Q179294), pangender (Q7130936), cogenitor (Q64017034), neutral sex (Q52261234), hermaphroditism (Q16674976), cisgender woman (Q15145779), cisgender man (Q15145778), third gender (Q48279), X-gender (Q96000630), demiboy (Q93954933), demigirl (Q93955709), bigender (Q859614), transgender (Q189125), travesti (Q17148251), 'akava'ine (Q4700377), assigned female at birth (Q56315990), assigned male at birth (Q25388691), androgyne (Q97595519), yinyang ren (Q8053770), boi (Q99519347), intersex person (Q104717073), gynandromorphism (Q430711), takatāpui (Q7677449), undisclosed gender (Q113124952), fakafifine (Q107427210), fakafafine (Q112597587), gender determined by the player (Q88293285), gender not disclosed in work (Q116254116), androgynos (Q4759445), intersex man (Q121307094), intersex woman (Q121307100), demimasc (Q121368243), futanari (Q123479538), altersex (Q59592239), gender unknown (Q116741172), gender agnostic (Q124637723): value must be one of the specified items. Please expand list if needed. (Help)
    List of violations of this constraint: Database reports/Constraint violations/P21#One of, values statistics, hourly updated report, SPARQL
    Conflicts with “coordinate location (P625): this property must not be used with the listed properties and values. (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Moko (Q107394029)
    List of violations of this constraint: Database reports/Constraint violations/P21#Conflicts with P625, SPARQL
    Conflicts with “located in the administrative territorial entity (P131): this property must not be used with the listed properties and values. (Help)
    List of violations of this constraint: Database reports/Constraint violations/P21#Conflicts with P131, hourly updated report, search, SPARQL
    Conflicts with “is a list of (P360): this property must not be used with the listed properties and values. (Help)
    List of violations of this constraint: Database reports/Constraint violations/P21#Conflicts with P360, hourly updated report, search, SPARQL
    Conflicts with “original language of film or TV show (P364): this property must not be used with the listed properties and values. (Help)
    List of violations of this constraint: Database reports/Constraint violations/P21#Conflicts with P364, hourly updated report, search, SPARQL
    Conflicts with “author (P50): this property must not be used with the listed properties and values. (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
    List of violations of this constraint: Database reports/Constraint violations/P21#Conflicts with P50, search, SPARQL
    Conflicts with “subclass of (P279): this property must not be used with the listed properties and values. (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: anonymous (Q4233718), video game character (Q1569167)
    List of violations of this constraint: Database reports/Constraint violations/P21#Conflicts with P279, search, SPARQL
    Conflicts with “has part(s) (P527): this property must not be used with the listed properties and values. (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Yuzu (Q75840084), Platon Kuzmich Koavalyov (Q55039999), Penthesilea (Q55052424), hitchBOT (Q17450611), Ötzi (Q171291)
    List of violations of this constraint: Database reports/Constraint violations/P21#Conflicts with P527, search, SPARQL
    Allowed entity types are Wikibase item (Q29934200), Wikibase MediaInfo (Q59712033): the property may only be used on a certain entity type (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
    List of violations of this constraint: Database reports/Constraint violations/P21#Entity types
    Scope is as main value (Q54828448), as qualifier (Q54828449): the property must be used by specified way only (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
    List of violations of this constraint: Database reports/Constraint violations/P21#Scope, SPARQL
    None of man (Q8441), masculine (Q499327), The Male Animal (Q3521737): value must not be any of the specified items.
    Replacement property:
    Replacement values: male (Q6581097) (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
    List of violations of this constraint: Database reports/Constraint violations/P21#none of, SPARQL
    None of woman (Q467), feminine (Q1775415), women in ancient Rome (Q1438918), Shosei (Q20040678): value must not be any of the specified items.
    Replacement property:
    Replacement values: female (Q6581072) (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
    List of violations of this constraint: Database reports/Constraint violations/P21#none of, SPARQL
    None of Xiong (Q108598090), (Q55814929): value must not be any of the specified items.
    Replacement property:
    Replacement values: male organism (Q44148) (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
    List of violations of this constraint: Database reports/Constraint violations/P21#none of, SPARQL
    None of (Q55814933), female connector (Q11659367): value must not be any of the specified items.
    Replacement property:
    Replacement values: female organism (Q43445) (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
    List of violations of this constraint: Database reports/Constraint violations/P21#none of, SPARQL
    Unsourced notname gender
    People with instance of (P31) set to notname (Q1747829) with an unsourced sex or gender (P21) set to male (Q6581097) (Help)
    Violations query: SELECT ?item WHERE { ?item wdt:P31 wd:Q1747829 . ?item p:P21 ?genderstatement . ?genderstatement ps:P21 wd:Q6581097 . MINUS { ?genderstatement prov:wasDerivedFrom ?source }. } LIMIT 1000
    List of this constraint violations: Database reports/Complex constraint violations/P21#Unsourced notname gender
    Fictional gender used on humans
    Humans with sex or gender (P21) set to an instance of fictional sex or gender (Q64017047) (Help)
    Violations query: SELECT ?item WHERE { ?item wdt:P31 wd:Q5; wdt:P21/wdt:P31* wd:Q64017047 }
    List of this constraint violations: Database reports/Complex constraint violations/P21#Fictional gender used on humans
    Value masculine (Q499327) will be automatically replaced to value male (Q6581097).
    Testing: TODO list
    Value boy (Q3010) will be automatically replaced to value male (Q6581097).
    Testing: TODO list
    Value man (Q8441) will be automatically replaced to value male (Q6581097).
    Testing: TODO list
    Value Männchen (Q1957296) will be automatically replaced to value male (Q6581097).
    Testing: TODO list
    Value Male (Q360210) will be automatically replaced to value male (Q6581097).
    Testing: TODO list
    Value husband (Q212878) will be automatically replaced to value male (Q6581097).
    Testing: TODO list
    Value woman (Q467) will be automatically replaced to value female (Q6581072).
    Testing: TODO list
    Value Feminine (Q251810) will be automatically replaced to value female (Q6581072).
    Testing: TODO list
    Value Female (Q639354) will be automatically replaced to value female (Q6581072).
    Testing: TODO list
    Value girl (Q3031) will be automatically replaced to value female (Q6581072).
    Testing: TODO list
    Value Weibchen (Q1304841) will be automatically replaced to value female (Q6581072).
    Testing: TODO list
    Value feminine (Q1775415) will be automatically replaced to value female (Q6581072).
    Testing: TODO list
    Value Female (Q63650079) will be automatically replaced to value female (Q6581072).
    Testing: TODO list
    Value Female (Q5442717) will be automatically replaced to value female (Q6581072).
    Testing: TODO list
    Value Female (Q5442715) will be automatically replaced to value female (Q6581072).
    Testing: TODO list
    Value Female (Q15600976) will be automatically replaced to value female organism (Q43445).
    Testing: TODO list
    Value stallion (Q757833) will be automatically replaced to value male organism (Q44148).
    Testing: TODO list
    Value male dog (Q105722362) will be automatically replaced to value male organism (Q44148).
    Testing: TODO list
    Value unknown (Q24238356) will be automatically replaced to value SOMEVALUE.
    Testing: TODO list
    Value unisex given name (Q3409032) will be automatically replaced to value unisex given name (Q3409032) and moved to instance of (P31) property.
    Testing: TODO list
    This property is being used by:

    Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

    Discussion edit

    Doesn't the conflation between sex and gender into a single category ruin the entire point of wikidata? edit

    It seems obvious to me that sex and gender (and possibly gender identity) should be distinct properties, if they are indeed different things. It'd be like combining a 'height or weight' property. It just... doesn't make much sense. Likewise, the related male/female/man/woman terms are also all horribly conflated, vague, and unclear. Which again seems like it ruins the entire point of the dataset. If "male" can refer to someone who is biologically female, how is that useful? Ultimately it seems the intended usage is for gender identity, and then assuming that unless otherwise stated, a person's sex is gender identity. IE an intentional conflation to avoid acknowledging that some people have a gender identity that differs from their sex. But... that's the entire definition of transgender, is it not? that their gender identity differs from their sex? Yet instead we see a solution being "transgender male" and "transgender female" which makes the distinction obvious, but the data more unwieldy. I also see that there's a distinction between human males and non-human males. This doesn't make much sense. It's not like the concept of maleness is somehow different in humans vs other animals.

    It's obvious that all of this gender identity stuff should have it's own property and values, which should ideally be named distinctly and differently from sex in order to differentiate them. I think it's obvious that some people are intentionally trying to conflate them, which causes problems with unambiguous datasets like what wikidata is attempting to achieve.

    Also noteworthy: Transsexualism should be distinct from Gender Identity Disorder. It appears that "transgender" typically refers to people with GID, however the definitions don't match this. Instead it seems that a fictitious concept of gender identity is coined and applied to everyone (despite it not being a thing) and then people using this as the justification for how GID and Gender Dysphoria result, when this is untrue. There is then further attempts to conflate Transgender/GID/Dysphoria with Transsexualism, and Gender Identity with Sex. And that is what has lead to the confusion and horribly unclear labeling. Each concept should have a distinct entry with clear and unambiguous definitions.

    Kafke (talk) 11:14, 2 February 2021 (UTC)Reply[reply]

    Akava'ine - can this be added? edit

    Hi all, I was adding someone to Wikidata, who is Akava'ine - which closely corresponds to the Samoan fa'afafine, a third gender in Pacific culture. Wikidata lets you add fa'afafine, but doesn't recognise Akava'ine as a constraint for gender. Please could it be added? Lajmmoore (talk) 15:06, 3 June 2021 (UTC)Reply[reply]

    @Lajmmoore: Looks like akava'ine was added in November 2021, so you should be able to add akava'ine as a field to biography items now. --Prosperosity (talk) 23:26, 26 May 2022 (UTC)Reply[reply]

    Citation needed constraint edit

    @Megs, Le Petit Chat: Since the property is highly used (7M+), I think it's better to discuss the possible addition of citation needed constraint (Q54554025) before applying it.

      Notified participants of WikiProject property constraints and I have reported the issue in WD:PC. --Epìdosis 19:21, 8 June 2021 (UTC)Reply[reply]

    I think that the real problem is for living people. It's better to create a Complex constraint instead of a citation needed constraint (Q54554025). Fralambert (talk) 22:14, 8 June 2021 (UTC)Reply[reply]
    See Property_talk:P21/Archive_1#Gender_is_central_for_forming_grammatical_sentences_and_as_such_needed.--GZWDer (talk) 04:40, 9 June 2021 (UTC)Reply[reply]
    Yeah, this property is essential for many Wikipedia language versions. We should be very careful not to complicate addition of this information too much, because almost all infoboxes in many Wikipedias (and probably other non-Wikipedia users in these languages too) rely on this property to display proper gender forms of words based on the subject's sex/gender. Requiring references would really complicate stuff.Vojtěch Dostál (talk) 04:47, 11 June 2021 (UTC)Reply[reply]

    Gender unkowned edit

    Dear all, sometimes I add some new zoologic authors but it happens (eg. Indian ones) that the first name can't be used to define the correct gender. For many times I putted "Male" with "hypothetical value" (like Q111133708) but I will prefer say "unkowned". Have you an idea to solve my problem. Thanks in advance. Givet (talk) 17:25, 24 March 2022 (UTC)Reply[reply]

    @Givet: just don't add any value! "Unknown value" means something different - that there are sources which have done some investigation and didn't find their gender. "Hypotheses" should be based upon some arguments, which do you have? --Infovarius (talk) 15:05, 25 March 2022 (UTC)Reply[reply]
    @Infovarius: - First of all, thanks for your reply. I add this information because if we try (on a species article) to connect an author without any gender information, we receive an error message. So how can I do? And, sorry, but I have no idea if, for example M. N. Acharji (like Q111133708) is a man or a woman. Givet (talk) 16:35, 25 March 2022 (UTC)Reply[reply]
    @Givet: Click edit, then an icon appears that looks like three boxes placed on top of one another. Click that icon and select "unknown value". See Help:Statements#Unknown or no values for more info. /Autom (talk) 10:19, 6 September 2022 (UTC)Reply[reply]
    @Autom: Of course ! You are totally right, I will use this method for the next times. I don't know why I was not thinking of this possibility, really better than an input of "Male/Female" with "perhaps". Thank you so much :-) Have a great day. Givet (talk) 15:26, 6 September 2022 (UTC)Reply[reply]
    @Autom: I tried a few seconds ago. First time I received an error message but when I retried another time, it works! (see Q113815418). Givet (talk) 16:30, 7 September 2022 (UTC)Reply[reply]

    guideline for anthropomorphic nonhumans? edit

    For example, both Q22983 and Q7823740 are listed as male despite both not being human.

    I would recommend adding some qualifier (eg. "or human-like") to the description, but I'm not sure. Binarycat64 (talk) 15:20, 30 March 2022 (UTC)Reply[reply]

    UK government combines sex and gender in forms edit

    Currently sex or gender (P21) is called "sex or gender". Lots of people have proposed separating these. Anyone can discuss more at wd:WikiProject LGBT.

    I want to share this 2018 discussion started by the government of the United Kingdom to manage gender or sex statements in government forms. It seems that wiki and the British government do the same thing of combining these concepts. They take comments in GitHub, and there I see arguments similar to the ones we have had on wiki.

    I do not see a solution here, but I see the UK government faced with the same problem. Bluerasberry (talk) 14:36, 9 June 2022 (UTC)Reply[reply]

    Wrong values about gender edit

    The description of the property states that for humans, it is possible to use "male, female, non-binary, intersex, transgender female, transgender male, agender." However, intersex is a biological sex rather than a gender identity. Besides, "trangender" is not a gender identity but the condition that a person does not identify with the gender that was assigned at birth. Somehow, saying that a "transgender female" is different from a "female" can be interpreted as an exclusion of trans women in the category of women (same applies to transgender males). Sjoel (talk) 14:23, 19 August 2022 (UTC)Reply[reply]

    • One possible solution for this exclusion issue would be to record two values, e.g. both female and transgender female, for those people who explicitly identify as transwomen. That allows searching for all women regardless of biological sex as well as trans women. AdamSeattle (talk) 22:01, 5 April 2023 (UTC)Reply[reply]

    Wikidata property example issue edit

    In the 'Wikidata property example' section here https://www.wikidata.org/wiki/Property:P1855 is listed as Female when at https://www.wikidata.org/wiki/Property:P1855 they are listed as Genderfluid. Suggest someone with edit rights make this light - but important! - edit. Drjwbaker (talk) 15:39, 5 December 2022 (UTC)Reply[reply]

    Overreaching Quickstatements/Bot Activity for P21 edit

    Editors have been observing a pattern of sex or gender (P21) statements being added for living people in ways that cause harm by misgendering. This is a gender issue, which has overlap with the LGBT+ community and with other types of personal demographic information which may violate privacy.

    Broad, ethically questionable additions of P21 statements using bots or Quickstatements is a problem mentioned in many of the discussions at Wikidata:WikiProject LGBT/gender. A recent group of large Quickstatements batches (example) demonstrated a need for a discussion surrounding best practices for assigning gender identities to living people on Wikidata. The editor responsible for these batches of edits collected Wikidata items for humans who did not have P21 values already, and who had been assigned given names listed in Wikidata as “female given name”. Given names are very frequently assigned to items for humans based on nothing more than their labels (see related discussion on user talk page for User:Jura1). The P21 values assigned were “female”, with a reference “based on heuristic: inferred from given name”. The edits were well-intentioned, with the stated purpose of increasing the representation of women on Wikidata.

    While the intention of increasing womens’ representation on Wikidata is a good one, the rationale behind these edits is dangerously flawed. A person’s given name is not a reliable indicator of that person’s gender identity. Performing blanket edits based on labels inevitably misgenders people. When the editor was approached, they responded by halting further ingests (how many edits were planned is unknown), but were not immediately willing to revert the tens of thousands of edits already made, saying, “I haven't mass-reverted yet, as I'd like to find wider consensus.”[1] Conversation continued on the user’s Wikidata talk page. Several Wikidata editors expressed and explained their ethical concerns about the edits that were made. One editor explained that the batch had added incorrect statements about many Tibetan people, and those errors were corrected individually. Another editor expressed that they themselves had been misgendered on Wikidata in the past by similar edits. The editor decided to revert the batches based on this feedback.

    A couple of subsequent conversations took place, with editors expressing pushback against reverting the edits in question. One user asked, “Instead of reversing heuristic genders, they have a very high rate of correctness, why not do the research to prove them right/wrong? If a given name is used by both genders, the formula does not assign a gender to that given name. You can also look for a primary/secondary source that mentions gender.” [2]. Once they discovered that the consensus appeared to lean towards reverting the changes, the same user stated, “We should probably look at error rates before making a decision, the error rate is most likely less than 1 in 1,000 based on the heuristic”. [3] This reasoning seems to be saying that since most affected people are unlikely to be harmed by misgendering, it’s ok for a minority of people to be harmed. It also seems to suggest that quality control and time-consuming research to verify the accuracy of huge batches of edits should not be the responsibility of the editor in charge of the batch, which seems irresponsible and unsustainable to me.

    It is not guaranteed (and is arguably unlikely) that corrections to bad data from such batches will ever happen given the enormity and difficulty of the task of verifying gender identities of hundreds of thousands of people. Furthermore, harm from misgendering cannot be entirely eliminated by reverting bad edits. Wikidata is quickly ingested into the Semantic web (a strength that draws people to Wikidata, but also a weakness where bad data is concerned). Additionally, bots and other Quickstatements users make edits based on data as it exists at the time of the edit. These secondary edits aren’t reverted when the data they were based on changes. The longer an editor “waits for consensus” before reverting, the higher the risk of harm being multiplied in this way.

    Myself and others have identified two proposals to limit swift, large-scale harm based on P21 moving forward:

    First, I would like to propose that bots and Quickstatements activity affecting more than ten items at a time be disallowed for P21. For properties that may violate privacy, the “edit first, ask questions later” approach is inappropriate and has already done a lot of harm. Where privacy may be violated or people may be harmed, “ask questions first” is a better approach. Is this something the Wikidata community can get behind?

    Second, I would like to propose that labels and given names not be accepted as references for P21 statements. I believe that this practice is unethical, harmful, and ought to be discouraged. Crystal Yragui, University of Washington Libraries (talk) 22:16, 29 March 2023 (UTC)Reply[reply]

    •   Support I support both of these proposals, for the reasons given. We need to be more careful with statements that could do harm or violate privacy than the bots/batch edits allow, and these proposals would help with that.
    Emwille (talk) 13:57, 30 March 2023 (UTC)Reply[reply]
    •   Support I also support both of these proposals for the reasons Crystal stated. We need to be more mindful of the ramifications of including sex/gender in general in my opinion.
    Sandrileine (talk) 18:51, 30 March 2023 (UTC)Reply[reply]
    •   Support I support both of these proposals. Batch edits should not be used for properties that may violate privacy and/or cause harm. Also, in many languages and cultures, names are not strictly gendered, so attempting to use them to infer gender doesn't even make sense and is likely to lead to misgendering. Regarding P21 in general, I think it is problematic that it conflates sex and gender in the first place. - Ɛs Huvər (talk) 21:28, 30 March 2023 (UTC)Reply[reply]
      Support -- Egon Willighagen (talk) 09:34, 1 April 2023 (UTC)Reply[reply]
      Support I agree that this should be a policy not to batch add sex or gender (P21) based solely on a given name. AdamSeattle (talk) 21:58, 5 April 2023 (UTC)Reply[reply]
      Oppose "that bots and Quickstatements activity affecting more than ten items at a time be disallowed for P21" - this needs to be dealt with on a case-by-case basis. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:39, 5 September 2023 (UTC)Reply[reply]

    Suggestions list edit

    Hi,

    at which place are the suggestions of P21 managed? Since a short period demigender (Q63715923) and gender unknown (Q116741172) are in front of male and female.

    It is illogical that the most common sex comes only at 4th place.--U. M. Owen (talk) 17:56, 21 August 2023 (UTC)Reply[reply]

    @Infovarius: Since you've just added curated Wikidata property (Q121928698): May I ask where the curation list is located?--U. M. Owen (talk) 05:07, 9 September 2023 (UTC)Reply[reply]
    I see the list at . I don't know what makes an order as present. --Infovarius (talk) 19:45, 10 September 2023 (UTC)Reply[reply]
    I've removed the Pokemon gender because it doesn't fit to the others. Let's see how this changes the suggestion list.--U. M. Owen (talk) 01:40, 16 September 2023 (UTC)Reply[reply]
    Now, multiple Pokémon-related items have a problem with this property. Maybe remove demigender, since no item currently has it as a gender/sex. MikutoH (talk) 01:23, 17 September 2023 (UTC)Reply[reply]
    It’s currently ordered by frequency for me. My display language is set to German right now, but I doubt that matters. Karl Oblique (talk) 12:40, 25 September 2023 (UTC)Reply[reply]
    Frequency of use probably shouldn't be the only consideration, since we want people to see undisclosed gender (Q113124952) and agender (Q505371) near the top of the list before they go to set the special 'no value' or 'unknown value' toggle. Arlo Barnes (talk) 21:26, 12 October 2023 (UTC)Reply[reply]

    The situation is still very unsatisfying. Some last added fictional porn genders like futanari appear now close to the top ahead of male and female. This must be changed. Male and female or vice versa must be on the top. Currently in English one hast to scroll down 9 lines to find female. Especially on small monitors and mobiles the scrolling is very time consuming if adding a lot of human beings. --Florentyna (talk) 12:22, 3 December 2023 (UTC)Reply[reply]

    I've reported the problem at Wikidata:Report a technical problem#sex or gender (P21) and suggestion list. Korg (talk) 14:18, 3 December 2023 (UTC)Reply[reply]
    As the person who added those fictional genders i am strongly against them being located at the near top. They should preferably be at the bottom Trade (talk) 12:22, 8 December 2023 (UTC)Reply[reply]
    Seems improved now... Arlo Barnes (talk) 05:38, 9 December 2023 (UTC)Reply[reply]
    Not really
    https://i.ibb.co/zG0xd7V/Screenshot-20231209-141434.png Trade (talk) 13:16, 9 December 2023 (UTC)Reply[reply]
    Weird, today it reverted for me also. But yesterday it was in the order shown in the one-of constraint... Arlo Barnes (talk) 20:20, 9 December 2023 (UTC)Reply[reply]

    Still crazy:   --Florentyna (talk) 19:55, 5 January 2024 (UTC)Reply[reply]

    Is there some magical creature behind the scene that controls the order of items suggested by properties? This is the only explanation i can think of since nobody on this site seems to have any control over it Trade (talk) 18:21, 17 January 2024 (UTC)Reply[reply]
    Return to "P21" page.