Property talk:P1114

Documentation

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

quantity
number of instances of this subject in the universe of the subject (the actual number of instances in Wikidata may be lower or higher)

Represents	number of objects (Q41792217)
Data type	Quantity
Template parameter	for example, "current_number" in en:Template:Infobox_subdivision_type
Domain	all (note: this should be moved to the property statements)
Allowed values	According to this template: most likely: positive integers According to statements in the property: 0 ≤ 𝓧 ≤ not applicable When possible, data should only be stored as statements
Allowed units	not applicable
Example	U.S. state (Q35657) → 50 Cities in Russia: Encyclopedia (Q28442534) → 50,000 Fabergé egg (Q331225) → 71
Robot and gadget jobs	DeltaBot does the following jobs: Move source to qualifier
Tracking: usage	Category:Pages using Wikidata property P1114 (Q21037774)
See also	proportion (P1107), numeric value (P1181), collection or exhibition size (P1436), number of works (P3740), number of records (P4876), number of branches (P8368), units sold (P2664)
Lists	<search Commons for files with depicts-statement and this property as qualifier> 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 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 Minimum and maximum Items with highest numeric value Items with lowest numeric value User:Laboramus/Units/P1114 (Units used) Database reports/Constraint violations/P1114 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 242,221 Main statement 12,095 5% of uses Qualifier 230,113 95% of uses Reference 13 <0.1% of uses

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

Qualifiers “end time (P582), start time (P580), point in time (P585), statement is subject of (P805), sourcing circumstances (P1480), including (P1012), excluding (P1011), nature of statement (P5102), announcement date (P6949), reason for deprecated rank (P2241), reason for preferred rank (P7452), criterion used (P1013), of (P642), has characteristic (P1552), Unicode range (P5949), applies to part (P518), valid in place (P3005), determination method (P459), lower limit (P5447), upper limit (P5448), distribution format (P437)”: 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). Known exceptions: LID milestone (Q55003547)
List of violations of this constraint: Database reports/Constraint violations/P1114#allowed qualifiers, SPARQL

Range from “0” to “+∞”: values should be in the range from “0” to “+∞”. (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/P1114#Range

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

Scope is as main value (Q54828448), 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/P1114#Scope, SPARQL

Units: “novalue”: value unit must be one of listed. (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/P1114#Units

This property is being used by: hu:Sablon:Autóbusz infobox, hu:Sablon:Villamos infobox hy:Կաղապար:Տեղեկաքարտ նկար, hy:Կաղապար:Տեղեկաքարտ քանդակ, hy:Կաղապար:Տեղեկաքարտ Արձան, hy:Կաղապար:Տեղեկաքարտ Նկար, hy:Կաղապար:Տեղեկաքարտ Պարգև d:Template:TR genea prop, d:Template:TR genea prop cem uk:Шаблон:Тип адміністративних одиниць, uk:Шаблон:Ядерне випробування, uk:Шаблон:Твір pt:Predefinição:Info/Jornal/Wikidata ca:Plantilla:Infotaula de polítop, ca:Plantilla:Infotaula equipament informàtic, ca:Plantilla:Infotaula vaixell/base, ca:Plantilla:Marató de TV3 eu:Txantiloi:Eraikin infotaula automatikoa, eu:Txantiloi:Eraikin infotaula be-x-old:Шаблён:Узнагарода, be-x-old:Шаблён:Газэта hyw:Կաղապար:Տեղեկաքարտ Արձան, hyw:Կաղապար:Տեղեկաքարտ Նկար es:Plantilla:Ficha de medalla be-tarask:Шаблён:Газэта, be-tarask:Шаблён:Узнагарода Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Generalizing this property

As per discussions about the need of a property to indicate the number of parts in a system, it has been suggested to generalize this property. The suggested label is "number of elements". If there are no objections I will change the label in a couple of days. See Wikidata:Property_proposal/Generic#number_of_parts.--Micru (talk) 07:25, 10 July 2014 (UTC)

I support the generalization (actually I thought the property could and was already used for that) but I am not sure "element" is very clear. It seem that train Xnumber of elementsfive could be used to mean that the train is made of 5 carriages. I have no better suggestion for a label though. --Zolo (talk) 08:54, 10 July 2014 (UTC)

@Zolo: That is not a problem because you can use qualifiers, for instance: <train> has part <carriage> with qualifier number of elements <5>. If you just say <train> number of elements <5>, it means that there are 5 trains.--Micru (talk) 09:18, 10 July 2014 (UTC)

@Micru:. I understand it is what is intended, but I am not sure that the word "element" makes it perfectly clear. "number of element of train X" seems to mean how many parts there are in a typical train X not how many instances of train X there are. . --Zolo (talk) 09:28, 10 July 2014 (UTC)

@Zolo: If you have any other suggestion I'll be glad to hear it. It could also be just "quantity" (in German it is already called "Anzahl", and we have it as alias now).--Micru (talk) 09:41, 10 July 2014 (UTC)

@Micru: Yes, perhaps simply "quantity" or even "number" as quantity might imply a measurement unit. --Zolo (talk) 09:53, 10 July 2014 (UTC)

I agree that dropping "of elements" is best. Like Zolo, I think "number" or "quantity" would be better, with the former being slightly better than the latter. Micru, thanks for taking the initiative on this! Emw (talk) 12:53, 15 July 2014 (UTC)

I've changed it to "quantity" because "number" is too ambiguous. The statement "number: 5" can be interpreted as this is the fifth of someting. /ℇsquilo 16:13, 8 September 2014 (UTC)

Good point, thanks. Emw (talk) 03:09, 11 September 2014 (UTC)

Using for a quantity of a medication

It has been proposed that we use this "quantity" for the "dose" of a medication.[1]

I am fine with that but we will need to remove the constraint for "integer constraint" and allow units like milligrams

Doc James (talk · contribs · email) 14:05, 17 November 2019 (UTC)

•  Support ArthurPSmith (talk) 18:56, 18 November 2019 (UTC)
• I don't think this is a good idea. The property is already suboptimal when not used as qualifier.

"quantity" is primarily a datatype .. so let's use it accordingly. --- Jura 12:02, 21 November 2019 (UTC)

@Jura1: For the record, it was meant to be used as a qualifier at proposal times, if I recall (but the creation discussion seems lost, actually). As the description states, it was primarily meant to represent the number of existing instances for a class (like human (Q5)) at a certain point in time (around 7 billions right now). It seems to have been renamed to « quantity » in english afterwards. Funny enough, there is a « quantity » proposal just below the proposal for this one that was rejected … weird mixup. author  TomT0m / talk page 12:15, 21 November 2019 (UTC)

It seems that the proposals were somewhat linked. Maybe some clean-up on current uses is needed. --- Jura 15:49, 22 November 2019 (UTC)