Property talk:P3150

Documentation

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

birthday
item for day and month on which the subject was born. Used when full "date of birth" (P569) isn't known.

Represents	birthday (Q47223)
Data type	Item
Template parameter	生月 and 生日 in w:ja:Template:ActorActress, 誕生日 in w:ja:Template:架空の人物, etc.
Domain	human (Q5), fictional character (Q95074), character that may or may not be fictional (Q21070598) or VTuber (Q55155641)
Usage notes	Use only when the subject's full "date of birth" (P569) isn't known.
Example	Naruto Uzumaki (Q931) → October 10 (Q2921) Tomosuke Funaki (Q5370772) → January 1 (Q2150) Steven Daniel (Q7614617) → January 4 (Q2168)
See also	date of birth (P569), day in year for periodic occurrence (P837)
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 Total of sitelinks on items Most identifiers Fewest 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 Map of people by place values: place of birth educated at work location residence place of death place of burial January 1st dates People with date of birth on January 1 People with date of death on January 1 People with both dates on January 1 Database reports/Complex constraint violations/P3150 Database reports/Constraint violations/P3150 Map Random list
Living people protection class	property that may violate privacy (Q44601380)
Proposal discussion	Proposal discussion
Current uses	Total 5,045 Main statement 4,654 92.2% of uses Qualifier 388 7.7% of uses Reference 3 <0.1% of uses
Search for values

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

Value type “point in time with respect to recurrent timeframe (Q14795564), calendar month (Q47018901)”: 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 point in time with respect to recurrent timeframe (Q14795564), calendar month (Q47018901) (or a subclass thereof). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Anna (Q15614636)
List of violations of this constraint: Database reports/Constraint violations/P3150#Value type Q14795564, Q47018901, SPARQL

Conflicts with “has part(s) (P527)”: this property must not be used with the listed properties and values. (Help)

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

Conflicts with “instance of (P31): twins (Q14756018), sibling duo (Q14073567), Wikimedia permanent duplicate item (Q21286738)”: 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/P3150#Conflicts with P31, 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).
List of violations of this constraint: Database reports/Constraint violations/P3150#Conflicts with P625, SPARQL

Single best value: this property generally contains a single value. If there are several, one would have preferred rank (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Larry Laffer (Q638630)
List of violations of this constraint: Database reports/Constraint violations/P3150#single best value, SPARQL

Type “human (Q5), fictional character (Q95074), character that may or may not be fictional (Q21070598), VTuber (Q55155641)”: item must contain property “instance of (P31)” with classes “human (Q5), fictional character (Q95074), character that may or may not be fictional (Q21070598), VTuber (Q55155641)” 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/P3150#Type Q5, Q95074, Q21070598, Q55155641, SPARQL

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/P3150#Scope, SPARQL

Qualifiers “determination method or standard (P459), sourcing circumstances (P1480), criterion used (P1013), reason for deprecated rank (P2241), statement disputed by (P1310), reason for preferred rank (P7452), statement supported by (P3680)”: this property should be used only with the listed qualifiers. (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/P3150#allowed qualifiers, SPARQL

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

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

Item “instance of (P31)”: Items with this property should also have “instance of (P31)”. (Help)

List of violations of this constraint: Database reports/Constraint violations/P3150#Item P31, hourly updated report, search, SPARQL

Citation needed: the property must have at least one reference (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/P3150#citation needed

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/P3150#Entity types

P569 with dateprecision 11
Items with this property generally wouldn't have P569 with full precision date (Help)
Violations query: SELECT ?item ?birthday ?date { ?item wdt:P3150 ?birthday . ?item p:P569 ?d . ?d psv:P569 ?datevalue . ?datevalue wikibase:timeValue ?date . ?datevalue wikibase:timePrecision 11 . ?d wikibase:rank ?rank .FILTER(?rank != wikibase:DeprecatedRank) FILTER ( ?item not in ( wd:Q4115189,wd:Q13406268,wd:Q15397819 ) ) } LIMIT 500
List of this constraint violations: Database reports/Complex constraint violations/P3150#P569 with dateprecision 11

P569 with dateprecision 9 or 10
Items with this property generally wouldn't have P569 with year of birth (and references of the same quality) (Help)
Violations query: SELECT ?item ?birthday ?date ?precision { ?item wdt:P3150 ?birthday . ?item p:P569 ?d . ?d psv:P569 ?datevalue . ?datevalue wikibase:timeValue ?date . ?datevalue wikibase:timePrecision ?precision . FILTER (?precision in (9, 10)) ?d wikibase:rank ?rank .FILTER(?rank != wikibase:DeprecatedRank) FILTER ( ?item not in ( wd:Q4115189,wd:Q13406268,wd:Q15397819 ) ) } LIMIT 500
List of this constraint violations: Database reports/Complex constraint violations/P3150#P569 with dateprecision 9 or 10

Discussion

Why not compatible with P569?

Why not use this even with entries that have date of birth (P569)? This would make queries like "who was born today" much easier. Laboramus (talk) 01:19, 17 April 2017 (UTC)

I'd argue that it's better to have to add a few extra characters of SPARQL code (example), than to have to add redundant statements to 2.9 million items, and then deal with the fallout of forking continually-changing data that's virtually impossible to accurately synchronize. --Yair rand (talk) 02:42, 5 December 2017 (UTC)

+1 with Yair rand. Cheers, VIGNERON (talk) 14:20, 5 October 2019 (UTC)

Add start/end period (P3415/P3416) as valid qualifiers

For people whose birthdays can only be narrowed down to a range of dates, using "start/end period" qualifiers to "unknown value" would be useful. For example, I've already used it a few times when I was only able to find someone's astrological sign. And unlike other "start/end" properties, "start/end period" don't require years, making them the best fit for this property. LadiesMakingComics (talk) 17:05, 28 March 2019 (UTC)