Property talk:P3781

From Wikidata
Jump to navigation Jump to search

Documentation

has active ingredient
has part biologically active component; inverse of "active ingredient in" (P3780)
Representsactive ingredient (Q912807)
Data typeItem
Domain
According to this template: chemical compounds of substances
According to statements in the property:
pharmaceutical product (Q28885102), chemical product (Q1069267) or chemical weapon (Q3639228)
When possible, data should only be stored as statements
Allowed valuesinstance of pharmaceutical product (Q28885102) (note: this should be moved to the property statements)
ExampleRoundup (Q905161)glyphosate (Q407232)
Afinitor (Q28890051)everolimus (Q421052)
Tylenol (Q3245302)paracetamol (Q57055)
SourceFDA, EMA, RxNorm (note: this information should be moved to a property statement; use property source website for the property (P1896))
See alsohas listed ingredient (P4543)
Lists
Proposal discussionProposal discussion
Current uses
Total2,764
Main statement2,76199.9% of uses
Qualifier30.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Inverse property of “active ingredient in (P3780):
if [item A] has this property (has active ingredient (P3781)) linked to [item B],
then [item B] should also have property “active ingredient in (P3780)” linked to [item A]. (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/P3781#inverse, 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/P3781#Scope, hourly updated report, SPARQL

Maybe this should be a subproperty of has listed ingredient (P4543). I'm not sure, because perhaps some product could have a known active ingredient but not officially specify it on the label. 98.33.89.204 03:29, 6 July 2020 (UTC)[reply]