Triple
T34658509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | yagé |
E890045
|
entity |
| Predicate | hasSecondaryIngredient |
P146042
|
FINISHED |
| Object | Psychotria viridis |
—
|
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: Psychotria viridis | Statement: [yagé, hasSecondaryIngredient, Psychotria viridis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryIngredient Context triple: [yagé, hasSecondaryIngredient, Psychotria viridis]
-
A.
hasSecondaryFlavor
Indicates that an entity possesses an additional, subordinate flavor characteristic beyond its primary flavor.
-
B.
hasSecondaryComponent
chosen
Indicates that an entity includes or is associated with an additional, subordinate component beyond its primary one.
-
C.
hasInactiveIngredient
Indicates that one entity contains another entity as a non-active (inactive) component or ingredient.
-
D.
hasKeyIngredientAttribute
Indicates that an entity possesses a specific key ingredient as a defining attribute or component.
-
E.
hasSecondary
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
- 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_69ffe12ee59c8190bc7da386e6d5332d |
completed | May 10, 2026, 1:36 a.m. |
| PD | Predicate disambiguation | batch_69ffe0a138bc8190a3d4b48cd579e985 |
completed | May 10, 2026, 1:34 a.m. |
Created at: May 1, 2026, 2:04 a.m.