Property talk:P111

Documentation

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

measured physical quantity
value of a physical property expressed as number multiplied by a unit

Description	physical property measured by an unit
Represents	physical quantity (Q107715)
Data type	Item
Domain	According to this template: unit of measurement (Q47574) According to statements in the property: unit of measurement (Q47574) or physical constant (Q173227) When possible, data should only be stored as statements
Allowed values	According to this template: physical quantity (Q107715) According to statements in the property: When possible, data should only be stored as statements
Example	minute (Q7727) → duration (Q2199864) kelvin (Q11579) → thermodynamic temperature (Q264647) hertz (Q39369) → frequency (Q11652) henry (Q163354) → inductance (Q177897) candela (Q83216) → luminous intensity (Q104831) mole (Q41509) → amount of substance (Q104946) siemens (Q169893) → electrical conductance (Q309017) lumen (Q484092) → luminous flux (Q107780) steradian (Q177612) → solid angle (Q208476) katal (Q208634) → catalytic activity (Q1735592) gray (Q190095) → absorbed dose (Q215313)
Tracking: usage	Category:Pages using Wikidata property P111 (Q26250022)
See also	measures (P2575), main subject (P921)
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 Database reports/Constraint violations/P111 Map Random list
Proposal discussion	[not applicable Proposal discussion]
Current uses	Total 3,880 Main statement 3,867 99.7% of uses Qualifier 13 0.3% of uses
Search for values

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

Type “unit of measurement (Q47574), physical constant (Q173227)”: item must contain property “instance of (P31), subclass of (P279)” with classes “unit of measurement (Q47574), physical constant (Q173227)” 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/P111#Type Q47574, Q173227, SPARQL

Value type “individual quantity (Q71550118)”: This property should use items as value that contain property “subclass of (P279)”. On these, the value for subclass of (P279) should be an item that uses subclass of (P279) with value individual quantity (Q71550118) (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/P111#Value type Q71550118, SPARQL

Scope is as main value (Q54828448): 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/P111#Scope, 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/P111#Entity types

Property “ISQ dimension (P4020)” declared by target items of “measured physical quantity (P111)”: If [item A] has this property with value [item B], [item B] is required to have property “ISQ dimension (P4020)”. (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/P111#Target required claim P4020, SPARQL, SPARQL (by value)

This property is being used by: it:Template:Infobox unità, it:Template:Unità, ca:Plantilla:Infotaula d'unitat scn:Template:Infobox unitati es:Plantilla:Ficha de organización religiosa, es:Plantilla:Wikidata Infobox gu:ઢાંચો:Wikidata Infobox, gu:ઢાંચો:Wikidata Infobox/core sv:Mall:Faktamall enhet, sv:Mall:Wikidata Infobox/core commons:Template:Wikidata Infobox/core cy:Nodyn:Wikidata Infobox id:Templat:Wikidata infobox, id:Templat:Kotak info Wikidata/inti mw:Template:Wikidata Infobox/core mr:साचा:विकिडाटा माहितीचौकट/core, mr:साचा:विकिडेटा माहितीचौकट/core sa:फलकम्:Wikidata Infobox ur:سانچہ:خانہ معلومات ویکی ڈیٹا/کور, ur:سانچہ:Wikidata Infobox/core q:fr:Modèle:Wikidata Infobox/core de:Vorlage:Wikidata Infobox/core ta:வார்ப்புரு:Wikidata Infobox/core eu:Txantiloi:Unitate infotaula hi:साँचा:Wikidata Infobox/core s:zh:Template:Wikidata Infobox/core ckb:داڕێژە:Wikidata Infobox/core pt:Predefinição:Wikidata Infobox/core ku:Şablon:Wikidata Infobox/core mnw:ထာမ်ပလိက်:Wikidata Infobox/core d:Template:Wikidata Infobox/core no:Mal:Wikidata Infobox/core s:ban:Mal:Wikidata Infobox/core ban:Mal:Wikidata Infobox/core lv:Veidne:Wikidata Infobox/core voy:shn:ထႅမ်းပလဵတ်ႉ:Wikidata Infobox s:hi:साँचा:Wikidata Infobox/core Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

label

Can I change the label to "measured physical quantity" (or just "measures") ? "Physical quantity" sounds rather ambiguous. --Zolo (talk) 08:45, 19 February 2013 (UTC)

I changed for de, en and fr. --Zolo (talk) 17:03, 19 February 2013 (UTC)

domain

I've run into this talkpage because find obvious that domain should be different. I see that P111 is redundant for units like kilowatt hour (Q182098) because they already have mention of quantity in instance of (P31) unit of energy (Q2916980). I propose to use current property only for subclasses of unit of measurement (Q47574), for example in unit of energy (Q2916980). --Infovarius (talk) 06:44, 24 April 2014 (UTC)

@Infovarius: Not all units have a class of the form "unit of <some physical quantity>". I would argue that those classes could be eliminated (not saying they should), given that their members can be derived (that is, queried) because each unit should have a value for measured physical quantity (P111). Toni 001 (talk) 12:57, 20 October 2019 (UTC)

"measured physical quantity"?

It now says "measured physical quantity". But it can also be a defined quantity. Alas. Actually, a better wording is: "value of a quantity" (that 'value' per SI is defined as: number × unit). All in all, the Wikidata handling of physical quantity and SI definition concepts is substandard. -DePiep (talk) 22:39, 23 December 2018 (UTC)

Measurement devices

A measuring instrument (Q2041172) measures a physical quantity (Q107715): For instance, a tide gauge (Q686697) measures height (Q208826) (of the tide). Given that the name of this property is currently "measured physical quantity" I propose to add measuring instrument (Q2041172) to the domain. Toni 001 (talk) 20:17, 18 October 2019 (UTC)

What about measures (P2575)? --Infovarius (talk) 19:39, 20 October 2019 (UTC)

@Infovarius: That's it, thanks. Toni 001 (talk) 19:39, 23 October 2019 (UTC)

wider scope

Some items has explicit relation to physical quantities (like Shore durometery (Q2035690), orders of magnitude (temperature) (Q182460))). I don't see any real obstacle to link them through P111 to quantities (what else? and why to have another property?), so I propose to remove constraint "should be unit". --Infovarius (talk) 03:13, 3 June 2020 (UTC)

We currently have the following connections:

1. P111: unit to quantity
2. P2575: measurement device to quantity
3. P1880: quantity to scale

The only things that don't fit in nicely at the moment are those "orders of magnitude" items. I'm not convinced that we should sacrifice the well-scopedness of any of those properties to squeeze in those items. Having tight constraints helps a lot with improving and maintaining the quality. Toni 001 (talk) 10:38, 3 June 2020 (UTC)

One-off constraint?

Hello @Jura1. What is the purpose of this edit? Why add a deprecated statement? Best wishes. Toni 001 (talk) 07:04, 23 March 2021 (UTC)

• The "reason for deprecation" is meant to explain it. Help:Property_constraints_portal/Entity_suggestions_from_constraint_definitions has more info. Deprecation avoids that it's actually a constraint being checked. --- Jura 08:10, 23 March 2021 (UTC)

I see, thanks. Toni 001 (talk) 08:47, 23 March 2021 (UTC)