Property talk:P3321
Documentation
- Start a query
- Current uses
- Statistics by class
- String length
- Language of strings
- List of qualifiers
- Count
male form of name or title
Description | male form of label | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Represents | masculine (Q499327) | |||||||||
Data type | Monolingual text | |||||||||
Domain | According to this template:
occupation (Q12737077) and position (Q4164871)
According to statements in the property:
When possible, data should only be stored as statementsprofession (Q28640), position (Q4164871), occupation (Q12737077), craft (Q2207288), hereditary title (Q5737899), noble title (Q355567), corporate title (Q11488158), kinship (Q171318), fictional profession (Q17305127), Wikidata property (Q18616576), family name (Q101352), title of honor (Q3320743), academic title (Q3529618), job title (Q828803), religious identity (Q4392985), demonym (Q217438), position (Q1781513), role (Q1707847), approbative (Q4781727), pejorative (Q545779), slur (Q22116852), ameliorative (Q1377295), human population (Q33829), class of ambassadors (Q29918287), inverse property label item (Q65932995), canonization status (Q15978876), Roman Catholic beatification and canonization stage (Q15978856), cohort (Q1303415), award (Q618779), political identity (Q3147836), ordinal number (Q191780), relative direction (Q2151613), role (Q214339), adjective (Q34698), role (Q4897819), cause of death (Q1931388), fictional analog of an occupation (Q115580828), person with an activity (Q129586023), fictional person with an activity (Q129586487), pet (Q39201), nobility of Spain (Q2554364) or person linked to the law (Q57735705) | |||||||||
Usage notes | Use P1560 for given names | |||||||||
Example | According to this template:
hétaïre (Q466118) → no value
When possible, data should only be stored as statementsacteur (Q33999) → fr"acteur" nephew or niece (Q76477) => en"nephew" frato / fratino (Q31184) => eo"frato" ondernemer (Q131524) → nl"zakenman" politikisto (Q82955) → io"politikistulo" dramatan (Q33999) → vo"hidramatan" ûndernimmer (Q131524) → fy"sakeman" | |||||||||
Robot and gadget jobs | it would be great to have one automatized sparql request listing feminine labels of title and functions which do not have a pending masculine label, and to enter the masculine form when it exist as well as notifying for the others that there is no feminine word associated. | |||||||||
Tracking: usage | Category:Pages using Wikidata property P3321 (Q126372543) | |||||||||
See also | given name version for other gender (P1560), female form of label (P2521), surname for other gender (P5278) | |||||||||
Lists | Help:Male form of label
| |||||||||
Proposal discussion | Proposal discussion | |||||||||
Current uses |
|
List of violations of this constraint: Database reports/Constraint violations/P3321#Scope, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3321#Conflicts with P31, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3321#Type Q28640, Q4164871, Q12737077, Q2207288, Q5737899, Q355567, Q11488158, Q171318, Q17305127, Q18616576, Q101352, Q3320743, Q3529618, Q828803, Q4392985, Q217438, Q1781513, Q1707847, Q4781727, Q545779, Q22116852, Q1377295, Q33829, Q29918287, Q65932995, Q15978876, Q15978856, Q1303415, Q618779, Q3147836, Q191780, Q2151613, Q214339, Q34698, Q4897819, Q1931388, Q115580828, Q129586023, Q129586487, Q39201, Q2554364, Q57735705, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3321#Item P2521, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3321#Entity types
List of violations of this constraint: Database reports/Constraint violations/P3321#allowed qualifiers, SPARQL
This property is being used by: Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
An item would generally have P2521 statement per language. TODO: define exceptions (Help)
Violations query:
SELECT ?item ?lang (COUNT(?monolingualstring) as ?count) (GROUP_CONCAT(?monolingualstring; separator=" // ") as ?list) { ?item wdt:P3321 ?monolingualstring . BIND(lang(?monolingualstring) as ?lang) FILTER ( ?item not in ( wd:Q4115189,wd:Q13406268,wd:Q15397819,wd:Q957729,wd:Q11631,wd:Q2259532,wd:Q33999,wd:Q30185 ) ) } GROUP BY ?item ?lang HAVING (?count > 1) ORDER BY DESC(?count) LIMIT 100
List of this constraint violations: Database reports/Complex constraint violations/P3321#Single value per language
Discussion
[edit]Distinct values constraint
[edit]@Robin van der Vliet: It looks like this property has a distinct values constraint, but female form of label (P2521) does not. It's also causing a violation at chairperson (Q140686) and chairperson (P488) when it should not be. Any thoughts on how to resolve? {{u|Sdkb}} talk 20:51, 18 August 2021 (UTC)
Why are item labels always male form?
[edit]I've launched the discussion here Wikidata:Project_chat#Why_are_labels_of_occupation_always_male_labels?. PAC2 (talk) 20:08, 27 October 2021 (UTC)
How to manage gender-specific form objects
[edit]With Q14625123, we noticed an issue : this object is only pertinent for one gender (male or female), and the only way to know this is to check label. However, this way is usable only humanly. Currently, no property or rank allow to check it. The goal would be to allow SPARQL request to include or exclude value in a unique and explicit way.
Several solutions can be used, but each one I think of need a modification in the current use:
- I do not see an existing rank for this kind of value, a specific rank could be created, as `N/A`
- a `N/A` standard Q value could be acceptable for Property:P3321 or Property:P2521
- a new property could be created, asserting that the object only is usable for male or female objects.
Do you have any other ideas? I made a suggestion in Property_talk:P2521#How_to_manage_gender-specific_form_objects for male or female specific term.
- All Properties
- Properties with monolingualtext-datatype
- Properties used on 10000+ items
- Properties with scope constraints
- Properties with conflicts with constraints
- Properties with constraints on type
- Properties with constraints on items using them
- Properties with entity type constraints
- Properties with qualifiers constraints
- Properties with complex constraints