Property talk:P3629

From Wikidata
Jump to navigation Jump to search

Documentation

age of subject at event
the age of the subject according to the cited source at the time of an event. Used as a qualifier of significant event property
Representsage of a person (Q185836)
Data typeQuantity
Domaincan be any animate, inanimate or fictional thing that can have an age (note: this should be moved to the property statements)
Allowed values
According to this template: number (default years if no units)
According to statements in the property:
0 ≤ 𝓧 ≤ 135
When possible, data should only be stored as statements
Allowed unitsyears old (Q24564698), week (Q23387), months old (Q73432674), days old (Q73432913), decades old (Q73433037) or centuries old (Q111037993)
Usage notesUsed as a qualifier of significant event property
Example
According to this template: To be used as a qualifier for any event.

Another example
According to statements in the property:
Tuomas Ketola (Q13541) → 36 years old
Theodore Roosevelt (Q33866) → 42 years old
Methuselah (Q156290) → 969 years old
When possible, data should only be stored as statements
See alsonarrative age (P6249)
Lists
Proposal discussionProposal discussion
Current uses
Total61,904
Main statement10,06516.3% of uses
Qualifier51,34182.9% of uses
Reference4980.8% of uses
[create Create a translatable help page (preferably in English) for this property to be included here]
Scope is as qualifier (Q54828449), as reference (Q54828450): 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/P3629#Scope, SPARQL
Range from “0” to “135”: values should be in the range from “0” to “135”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Elros (Q1637307)
List of violations of this constraint: Database reports/Constraint violations/P3629#Range
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/P3629#Units
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/P3629#Entity types

Constraint as qualifier only is problematic[edit]

There are times when this property needs to be used as a qualifier in a reference, so the constraint that this should only be used as a qualifier to the item is a problem. For instance, if someone is mentioned with an age in a census record which would support a year of birth, that needs to be against the reference not the birth event.  — billinghurst sDrewth 22:59, 4 March 2018 (UTC)[reply]

@Pasleim: it would appear you initially applied the constraint. Is there an alternative way to label this to indicate this duality?  — billinghurst sDrewth 23:02, 4 March 2018 (UTC)[reply]
Example at Q18912183  — billinghurst sDrewth 23:03, 4 March 2018 (UTC)[reply]

It was proposed as a qualifier. Maybe with the new qualifier constraint scope we can specify that it can also be used in references.
--- Jura 05:04, 5 March 2018 (UTC)[reply]

Another example special:diff/Q18911087 where I have two references for time specific references in primary records.  — billinghurst sDrewth 07:38, 11 March 2018 (UTC)[reply]

removed "allowed units constraint"[edit]

I have removed the constraint "allowed units constraint" as it doesn't make sense in the remainder of the context of the property as shows. Firstly there is a maximum value of 130, so that presumes that years old is the constraint unless otherwise specific, and doesn't make sense for anything else. It was also showing a constraint error where used, and yet the value shows that a unit is optional. Please can we resolve these issues prior to adding the constraint back.  — billinghurst sDrewth 14:21, 28 April 2018 (UTC)[reply]

Bot to add at date of death[edit]

Can we have a bot add the value at date of death for all humans, where we have precise birth and death dates? It would be valuable in disambiguating people without doing any math. RAN (talk) 00:44, 2 May 2023 (UTC)[reply]