Triple
T34658623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caapi |
E890047
|
entity |
| Predicate | roleInAyahuasca |
P202974
|
FINISHED |
| Object | primary ingredient |
—
|
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: primary ingredient | Statement: [Caapi, roleInAyahuasca, primary ingredient]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInAyahuasca Context triple: [Caapi, roleInAyahuasca, primary ingredient]
-
A.
roleInRitual
Indicates the specific function, position, or responsibility an entity holds within a particular ritual or ceremonial activity.
-
B.
roleInScientology
Indicates that one entity holds or has held a specific position, function, or status within the organizational or religious structure of Scientology in relation to another entity.
-
C.
roleInCoco
Indicates that an entity serves a specific role or function within the context of the COCO dataset or framework.
-
D.
roleInMacondo
Indicates the specific function, position, or significance an entity holds within the context of Macondo.
-
E.
roleInTauris
Indicates that an entity has a specific role or function within the context of Tauris (e.g., a work, setting, or domain associated with Tauris).
- F. None of above. chosen
Provenance (4 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_6a00d76d0e0881908d83a8dcce511167 |
completed | May 10, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_6a00d711805881909a94cfd1f25fb331 |
completed | May 10, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a00d76bde6c81909e564ab9cb0325af |
completed | May 10, 2026, 7:07 p.m. |
Created at: May 1, 2026, 2:04 a.m.