Triple
T34658550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | yagé |
E890045
|
entity |
| Predicate | hasPharmacologicalProperty |
P178222
|
FINISHED |
| Object | MAO-inhibiting |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: MAO-inhibiting | Statement: [yagé, hasPharmacologicalProperty, MAO-inhibiting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPharmacologicalProperty Context triple: [yagé, hasPharmacologicalProperty, MAO-inhibiting]
-
A.
hasPharmacologicalEffect
Indicates that one entity produces a specific pharmacological effect or action on another entity.
-
B.
pharmacologicalProfile
chosen
Indicates the relationship between a substance and the set of its pharmacological properties, including mechanisms of action, effects, and interactions in a biological system.
-
C.
hasPharmacologicClass
Indicates that a drug or medicinal product belongs to a specific pharmacologic class based on its mechanism of action or therapeutic effect.
-
D.
hasDrugBankID
Indicates that an entity is associated with a specific identifier from the DrugBank database.
-
E.
hasChemicalProperty
Indicates that an entity possesses or exhibits a specific chemical property or characteristic.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f349d906bc8190b2efd9eff237d94b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 1, 2026, 2:04 a.m.