Property talk:P1533

Documentation

• Start a query
• Current uses
• Statistics by class
• List of values
• List of qualifiers
• Count

family name identical to this given name
last name that is the same as a given first name. Use on items for given names

Description	The surname/family name spelled the same was as this given name/first name is:
Data type	Item
Domain	given name (Q202444)
Allowed values	family name (Q101352) (note: this should be moved to the property statements)
Example	Louis (Q2897866) → Louis (Q15728984) Sylvain (Q16281827) → Sylvain (Q18001608)
Tracking: usage	Category:Pages using Wikidata property P1533 (Q126375080)
See also	Scandinavian middle family name (P6978)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties By value of property Most statements Fewest statements Most sitelinks Most linked wikis Most identifiers Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Database reports/Complex constraint violations/P1533 Database reports/Constraint violations/P1533 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 21,020 Main statement 21,017 >99.9% of uses Qualifier 2 <0.1% of uses Reference 1 <0.1% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Single value: this property generally contains a single value. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Kane (Q43400770), Tullus (Q2409346), Primus (Q2611153)
List of violations of this constraint: Database reports/Constraint violations/P1533#Single value, SPARQL

Type “given name (Q202444)”: item must contain property “instance of (P31)” with classes “given name (Q202444)” or their subclasses (defined using subclass of (P279)). (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/P1533#Type Q202444, SPARQL

Value type “family name (Q101352)”: This property should use items as value that contain property “instance of (P31)”. On these, the value for instance of (P31) should be an item that uses subclass of (P279) with value family name (Q101352) (or a subclass thereof). (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/P1533#Value type Q101352, SPARQL

Conflicts with “instance of (P31): Wikimedia disambiguation page (Q4167410), family name (Q101352)”: this property must not be used with the listed properties and values. (Help)

List of violations of this constraint: Database reports/Constraint violations/P1533#Conflicts with P31, hourly updated report, SPARQL

Conflicts with “given name (P735)”: this property must not be used with the listed properties and values. (Help)

List of violations of this constraint: Database reports/Constraint violations/P1533#Conflicts with P735, hourly updated report, search, SPARQL

Conflicts with “family name (P734)”: this property must not be used with the listed properties and values. (Help)

List of violations of this constraint: Database reports/Constraint violations/P1533#Conflicts with P734, hourly updated report, search, SPARQL

Conflicts with “father (P22)”: this property must not be used with the listed properties and values. (Help)

List of violations of this constraint: Database reports/Constraint violations/P1533#Conflicts with P22, hourly updated report, search, SPARQL

Conflicts with “mother (P25)”: this property must not be used with the listed properties and values. (Help)

List of violations of this constraint: Database reports/Constraint violations/P1533#Conflicts with P25, hourly updated report, search, SPARQL

Conflicts with “stepparent (P3448)”: this property must not be used with the listed properties and values. (Help)

List of violations of this constraint: Database reports/Constraint violations/P1533#Conflicts with P3448, hourly updated report, search, SPARQL

Conflicts with “sibling (P3373)”: 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/P1533#Conflicts with P3373, search, SPARQL

Conflicts with “spouse (P26)”: this property must not be used with the listed properties and values. (Help)

List of violations of this constraint: Database reports/Constraint violations/P1533#Conflicts with P26, hourly updated report, search, SPARQL

Conflicts with “unmarried partner (P451)”: this property must not be used with the listed properties and values. (Help)

List of violations of this constraint: Database reports/Constraint violations/P1533#Conflicts with P451, hourly updated report, search, SPARQL

Conflicts with “child (P40)”: 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/P1533#Conflicts with P40, search, SPARQL

Conflicts with “relative (P1038)”: this property must not be used with the listed properties and values. (Help)

List of violations of this constraint: Database reports/Constraint violations/P1533#Conflicts with P1038, 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/P1533#Conflicts with P364, hourly updated report, search, SPARQL

Conflicts with “official website (P856)”: this property must not be used with the listed properties and values. (Help)

List of violations of this constraint: Database reports/Constraint violations/P1533#Conflicts with P856, hourly updated report, 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/P1533#Conflicts with P360, hourly updated report, search, SPARQL

Conflicts with “GeoNames ID (P1566)”: this property must not be used with the listed properties and values. (Help)

List of violations of this constraint: Database reports/Constraint violations/P1533#Conflicts with P1566, hourly updated report, search, SPARQL

Conflicts with “MusicBrainz artist ID (P434)”: this property must not be used with the listed properties and values. (Help)

List of violations of this constraint: Database reports/Constraint violations/P1533#Conflicts with P434, hourly updated report, search, SPARQL

Conflicts with “canonization status (P411)”: this property must not be used with the listed properties and values. (Help)

List of violations of this constraint: Database reports/Constraint violations/P1533#Conflicts with P411, hourly updated report, search, SPARQL

Conflicts with “occupation (P106)”: this property must not be used with the listed properties and values. (Help)

List of violations of this constraint: Database reports/Constraint violations/P1533#Conflicts with P106, hourly updated report, search, SPARQL

Distinct values: this property likely contains a value that is different from all other items. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Q493293, Q18177306, Q18177321, Q325872, Q25413386, Q18620539, Q18620536, Q12901049, Q18635485, Q18635486, Q659189, Q25999849, Q2611153, Q47531277, Q10545745, Q90148594, Q66264057, Q1300961, Q54617672, Q1667498, Q104546007, Q98841742, Q20817465, Q30086406, Q28053272, Q18010311, Q18686588, Q18689525, Q18552031, Q1559648, Q18220903, Q12173670, Q18219684, Q16652258
List of violations of this constraint: Database reports/Constraint violations/P1533#Unique value, SPARQL (every item), SPARQL (by value)

Item “language of work or name (P407)”: Items with this property should also have “language of work or name (P407)”. (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/P1533#Item P407, search, SPARQL

Item “native label (P1705)”: Items with this property should also have “native label (P1705)”. (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/P1533#Item P1705, SPARQL

Property “native label (P1705)” declared by target items of “family name identical to this given name (P1533)”: If [item A] has this property with value [item B], [item B] is required to have property “native label (P1705)”. (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/P1533#Target required claim P1705, SPARQL, SPARQL (by value)

Scope is as main value (Q54828448): the property must be used by specified way only (Help)

List of violations of this constraint: Database reports/Constraint violations/P1533#Scope, hourly updated report, SPARQL

Allowed entity types are Wikibase item (Q29934200): 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/P1533#Entity types

Missing statements (male given name)
add P1533 (Help)
Violations query: SELECT ?item ?fam WHERE { ?fam wdt:P31 wd:Q101352 . MINUS { ?fam ^ wdt:P1533 [] } ?fam rdfs:label ?fn . FILTER(lang(?fn)="en") ?item rdfs:label ?fn . ?item wdt:P31 wd:Q12308941 . FILTER( ?item != ?fam ) ?fam wdt:P282 wd:Q8229 . ?item wdt:P282 wd:Q8229 . FILTER NOT EXISTS { ?item wdt:P31 wd:Q4167410 } FILTER NOT EXISTS { ?fam wdt:P31 wd:Q4167410 } } LIMIT 50
List of this constraint violations: Database reports/Complex constraint violations/P1533#Missing statements (male given name)

Missing statements (female given name)
add P1533 (Help)
Violations query: SELECT ?item ?fam WHERE { ?fam wdt:P31 wd:Q101352 . MINUS { ?fam ^ wdt:P1533 [] } ?fam rdfs:label ?fn . FILTER(lang(?fn)="en") ?item rdfs:label ?fn . ?item wdt:P31 wd:Q11879590 . FILTER( ?item != ?fam ) ?fam wdt:P282 wd:Q8229 . ?item wdt:P282 wd:Q8229 . FILTER NOT EXISTS { ?item wdt:P31 wd:Q4167410 } FILTER NOT EXISTS { ?fam wdt:P31 wd:Q4167410 } } LIMIT 50
List of this constraint violations: Database reports/Complex constraint violations/P1533#Missing statements (female given name)

Missing statements (given name)
add P1533 (Help)
Violations query: SELECT ?item ?fam WHERE { ?fam wdt:P31 wd:Q101352 . MINUS { ?fam ^ wdt:P1533 [] } ?fam rdfs:label ?fn . FILTER(lang(?fn)="en") ?item rdfs:label ?fn . ?item wdt:P31 wd:Q202444 . FILTER( ?item != ?fam ) ?fam wdt:P282 wd:Q8229 . ?item wdt:P282 wd:Q8229 . FILTER NOT EXISTS { ?item wdt:P31 wd:Q4167410 } FILTER NOT EXISTS { ?fam wdt:P31 wd:Q4167410 } } LIMIT 50
List of this constraint violations: Database reports/Complex constraint violations/P1533#Missing statements (given name)

Missing statements (unisex given name)
add P1533 (Help)
Violations query: SELECT ?item ?fam WHERE { ?fam wdt:P31 wd:Q101352 . MINUS { ?fam ^ wdt:P1533 [] } ?fam rdfs:label ?fn . FILTER(lang(?fn)="en") ?item rdfs:label ?fn . ?item wdt:P31 wd:Q3409032 . FILTER( ?item != ?fam ) ?fam wdt:P282 wd:Q8229 . ?item wdt:P282 wd:Q8229 . FILTER NOT EXISTS { ?item wdt:P31 wd:Q4167410 } FILTER NOT EXISTS { ?fam wdt:P31 wd:Q4167410 } } LIMIT 50
List of this constraint violations: Database reports/Complex constraint violations/P1533#Missing statements (unisex given name)

This property is being used by: hy:Կաղապար:Տեղեկաքարտ Անուն hyw:Կաղապար:Տեղեկաքարտ Անուն ca:Plantilla:Infotaula de nom d:Template:TP given name Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Constraint:Unique value disputed

An example at Talk:Q18177306#Property:P1533 questions validity of this constraint, because it is clear that the discussed issue may affect more items in the future. I prefer keeping the constraint and removing redundant claims. Petr Matas 11:27, 18 November 2014 (UTC)

I agree to keep it, but I'd just add exceptions to the list for such. --- Jura 11:31, 18 November 2014 (UTC)

I think that adding exceptions is unsystematic, because the list will probably get quite longer in the future. Your opposition to removing useful (though redundant) information is valid, but I think that getting rid of the exceptions outweights it. Petr Matas 11:50, 18 November 2014 (UTC)

If the lists gets long, one could just create a new constraint that handles it better. Constraints are just approximations that help us improve the data. They are not necessarily ideal for every property.

BTW, I don't think you addressed the points raised on Talk:Q18177306#Property:P1533. --- Jura 07:13, 19 November 2014 (UTC)

I did not address them because I consider them valid. I also agree that having only a few exceptions is not a problem. However, may we mark the constraint as mandatory in that case? Petr Matas 09:10, 19 November 2014 (UTC)

Ok. I think one can't currently combine "mandatory=true" with a list of exceptions. --- Jura 14:42, 19 November 2014 (UTC)

I've just looked at the template doc, where I found a sample, which combines them. I'd really like to make the constraint mandatory. Petr Matas 15:21, 19 November 2014 (UTC)

This is how you can get the corresponding family name of Andrea (Q18177306) even if it is mentioned only in its superclass: Query: tree[18177306[279] and claim[1533] &props=1533]. Petr Matas 22:26, 19 November 2014 (UTC)

Aligned English labels

The intermix of first and given between the main label and this can be a little confusing, so I have changed this to match the main "given name".  — billinghurst sDrewth 21:06, 4 January 2017 (UTC)

Inverse property?

I'm wondering why there is no inverse property for this one, for linking from family names to given names. Should I propose one?

Ash Crow
Dereckson
Harmonia Amanda
Hsarrazin
Jura
Чаховіч Уладзіслаў
Joxemai
Place Clichy
Branthecan
Azertus
Jon Harald Søby
PKM
Pmt
Sight Contamination
MaksOttoVonStirlitz
BeatrixBelibaste
Moebeus
Dcflyer
Looniverse
Aya Reyad
Infovarius
Tris T7
Klaas 'Z4us' van B. V
Deborahjay
Bruno Biondi
ZI Jony
Laddo
Da Dapper Don
Data Gamer
Luca favorido
The Sir of Data Analytics
Skim
E4024
JhowieNitnek
Envlh
Susanna Giaccai
Epìdosis
Aluxosm
Dnshitobu
Ruky Wunpini
Balû
★Trekker

Notified participants of WikiProject Names Jon Harald Søby (talk) 09:48, 15 August 2017 (UTC)

I don't see why we would need one? What would a reverse property do that we can't do right now? (except creating more work, that is). --Harmonia Amanda (talk) 18:30, 15 August 2017 (UTC)

@Harmonia Amanda: In automatic infoboxes for family names, you could link automatically to the identical first names. I don't know how you can do that currently? Jon Harald Søby (talk) 09:48, 16 August 2017 (UTC)

Well with lua? You ask for the item(s) linked to this item using this property, instead of asking for the value of the property. It should work perfectly? --Harmonia Amanda (talk) 17:36, 16 August 2017 (UTC)

@Harmonia Amanda: Where, how? Special:Whatlinkshere and queries are not available through Lua yet! -- Innocent bystander (talk) 07:10, 17 August 2017 (UTC)

@Jon Harald Søby: I don't see why we shouldn't! I say propose it. There's lots of precedence for symmetrical properties and automated editing would lighten most of the extra work load. --Azertus (talk) 13:16, 12 September 2018 (UTC)