Triple
T34658916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barquinha |
E890053
|
entity |
| Predicate | coreRitualSubstance |
P107739
|
FINISHED |
| Object | ayahuasca |
—
|
NE NERFINISHED |
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: ayahuasca | Statement: [Barquinha, coreRitualSubstance, ayahuasca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreRitualSubstance Context triple: [Barquinha, coreRitualSubstance, ayahuasca]
-
A.
substancePersonified
Indicates that an abstract substance or concept is represented or treated as if it were a person or sentient being.
-
B.
substanceType
Indicates the specific kind or category of substance associated with an entity or relation.
-
C.
hasRitualElements
Indicates that one entity incorporates, contains, or is characterized by ritualistic components, practices, or features associated with formalized ceremonies or rites.
-
D.
hasFictionalSubstance
Indicates that one entity includes, contains, or involves a fictional or imaginary substance as part of its composition, setting, or narrative.
-
E.
ritualPlant
chosen
Indicates that a plant is used or involved in a ritual, ceremony, or other formalized spiritual or cultural practice.
- 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_69f722cb433c81909bf0058b5845f5c2 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.