Property talk:P3452

Documentation

• Start a query
• Properties using this qualifier (statistics)
• Count

inferred from
statement added based on related statement found within the item, not the entity described by the item (to be used in a reference field)

Represents	source of information (Q3523102)
Data type	Item
Usage notes	This property indicates that the information is contained within the provided item itself, as part of its statements. If you want to express that the information is contained by the entity (a book, an article, etc) that's represented by the linked information source, use P248.
Robot and gadget jobs	DeltaBot does the following jobs: Move qualifier to source
Tracking: usage	Category:Pages using Wikidata property P3452 (Q98131256)
See also	stated in (P248), item inherits statement from (P5852), based on heuristic (P887), opposite of (P461)
Lists	list of Wikidata heuristics (Q130369576) Most recently created items Items with novalue claims Items with unknown value claims Items with deprecated claims Usage history (total) Usage history (main statement) Database reports/Complex constraint violations/P3452 Database reports/Constraint violations/P3452
Proposal discussion	Proposal discussion
Current uses	Total 1,021,346 Main statement 7 <0.1% of uses Qualifier 6 <0.1% of uses Reference 1,021,333 >99.9% of uses

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

Scope is as reference (Q54828450): the property must be used by specified way only (Help)

List of violations of this constraint: Database reports/Constraint violations/P3452#Scope, hourly updated report, search (main only), SPARQL

Allowed entity types are Wikibase item (Q29934200), Wikibase lexeme (Q51885771), Wikibase MediaInfo (Q59712033), Wikibase property (Q29934218), Wikibase form (Q54285143), Wikibase sense (Q54285715): 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/P3452#Entity types

Two inverse statements inferred from each other
Two inverse statements inferred from each other (Help)
Violations query: SELECT ?item WHERE { ?property_1 wikibase:claim ?property_1_claim; wikibase:statementProperty ?property_1_ps; p:P2302 [ ps:P2302 wd:Q21510855; pq:P2306 ?property_2 ] . ?property_2 wikibase:claim ?property_2_claim; wikibase:statementProperty ?property_2_ps; p:P2302 [ ps:P2302 wd:Q21510855; pq:P2306 ?property_1 ]. ?item ?property_1_claim [ ?property_1_ps ?target; prov:wasDerivedFrom / pr:P3452 ?target ]. ?target ?property_2_claim [ ?property_2_ps ?item; prov:wasDerivedFrom / pr:P3452 ?item ]. }
List of this constraint violations: Database reports/Complex constraint violations/P3452#Two inverse statements inferred from each other

Value inferred from person's given name (Q69652498) will be automatically replaced to value inferred from person's given name (Q69652498) and moved to based on heuristic (P887) property. Testing: TODO list

To do

Things that might need conversion to this new property:

• : , imported from Wikimedia project (P143)
• : , stated in (P248)
•  Done imported from Wikimedia project (P143): Wikidata (Q2013). Sample: Q12142918
•  Done imported from Wikimedia project (P143): Q20651139
• reference URL (P854): <https://www.wikidata.org/wiki/Q####>. Sample: Q53016

Discussion

Conversion of previous approaches

Above I started a list of things that should probably be converted to this (no longer really) new property.
--- Jura 14:15, 17 October 2017 (UTC)

Is this property just a new imported from Wikimedia project (P143)?

Hi, there are lots of statements that is inferred from (P3452) Wikimedia category (Q4167836). Is it a proper usage of this property? Is this property supposed to be more reliable than imported from Wikimedia project (P143), or just another imported from Wikimedia project (P143)?--Midleading (talk) 07:45, 10 December 2019 (UTC)

In cases where the category only has one sitelink, the statement could be converted to be an 'imported from' statement for that project. Where there are more than one, you could still say that the statement is 'imported from' each of them in turn (as long as it's true -- that is, if the content is comparable in each case) but at some point it gets unwieldy. I do think in cases where 'imported from' and 'inferred from' are equivalent, 'imported from' should be preferred because the companion property 'import URL' can point to an oldid, whereas 'inferred from' is always vulnerable to change in the target item. Arlo Barnes (talk) 20:34, 15 November 2021 (UTC)