Property talk:P2218

From Wikidata
Jump to navigation Jump to search

Documentation

DescriptionWealth a person has
Representsnet worth (Q1933764)
Data typeQuantity
Template parameternet_worth in w:Template:Infobox person
Domain
According to this template: people
According to statements in the property:
person (Q215627), enterprise (Q6881511) or fictional character (Q95074)
When possible, data should only be stored as statements
Allowed values−150,000,000,000 ≤ 𝓧 ≤ 500,000,000,000
Allowed unitsInstances of: currency
United States dollar (Q4917), guilder (Q203607), pound sterling (Q25224), Euro (Q4916), Australian dollar (Q259502), Canadian dollar (Q1104069), Czech koruna (Q131016), renminbi (Q39099), yen (Q8146), renminbi (offshore) (Q73015708), rupiah (Q41588), Malaysian ringgit (Q163712), Philippine peso (Q17193), Swedish krona (Q122922) or Egyptian pound (Q199462)
ExampleJeff Bezos (Q312556) → 113,500,000,000 United States dollar
Sourceinfoboxes (note: this information should be moved to a property statement; use property source website for the property (P1896))
Tracking: usageCategory:Pages using Wikidata property P2218 (Q27056198)
See alsototal assets (P2403)
Lists
Living people protection classproperty that may violate privacy (Q44601380)
Proposal discussionProposal discussion
Current uses
Total1,819
Main statement1,818>99.9% of uses
Qualifier1<0.1% of uses
[create Create a translatable help page (preferably in English) for this property to be included here]
Range from “-150000000000” to “500000000000”: values should be in the range from “-150000000000” to “500000000000”. (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/P2218#Range
Type “person (Q215627), enterprise (Q6881511), fictional character (Q95074): item must contain property “instance of (P31)” with classes “person (Q215627), enterprise (Q6881511), fictional character (Q95074)” 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/P2218#Type Q215627, Q6881511, Q95074, SPARQL
Qualifiers “point in time (P585), reason for deprecated rank (P2241), reason for preferred rank (P7452), sourcing circumstances (P1480): 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/P2218#allowed qualifiers, SPARQL
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/P2218#Scope, hourly updated report, 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/P2218#citation needed
Required qualifier “point in time (P585): this property should be used with the listed qualifier. (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/P2218#mandatory qualifier, 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/P2218#Entity types

Should we enforce some guidelines in regards to sourcing?[edit]

Anecdotally it seems this property is used a lot for celebrities and that the numbers come from gossip websites, rather than Forbes or any other "reputable" financial publications or government registries. Rick Rubin is worth 250.000.000 USD according to us, for Rubin's sake I hope that is true, but should we keep statements like these when not sourced in any way? Would it be an idea to set up some guidelines on how to use this property, some constraints maybe, link the statement to a point in time, deal with currency conversion, etc.? Discuss! Moebeus (talk) 14:13, 4 August 2020 (UTC)[reply]

Good find! Yes, we should come up with some sort of guideline. By the way, is it technically possible to create a property constraint to require a source? Ainali (talk) 14:19, 4 August 2020 (UTC)[reply]

Why "estimated"[edit]

I guess we are so used to estimates of peoples' wealth that the concepts have virtually fused. But in principle, net worth can be measured to any arbitrary precision. There are many values where we know that the best available data comes with some uncertainty, such as population (P1082) or GDP (PPP) (P4010). And yet, those do not come with the "estimate" moniker. In any case, there is estimate (Q37113960) to qualify such statements, with added benefits such as nuanced alternatives. --Matthias Winkelmann (talk) 09:35, 21 September 2020 (UTC)[reply]

allowed units constraint[edit]

Why the list of allowed currencies is limited only by those? Wolverène (talk) 05:12, 8 August 2023 (UTC)[reply]