Triple
T34658801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santo Daime |
E890051
|
entity |
| Predicate | hasMainSacrament |
P1111
|
FINISHED |
| Object | ayahuasca |
—
|
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: ayahuasca | Statement: [Santo Daime, hasMainSacrament, ayahuasca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainSacrament Context triple: [Santo Daime, hasMainSacrament, ayahuasca]
-
A.
sacramentFunction
Indicates that one entity serves as a religious sacrament or sacred rite performed or administered in relation to another entity.
-
B.
principalSacrament
chosen
Indicates that one sacrament holds primary or highest importance in relation to another or within a given religious or ritual context.
-
C.
includesSacrament
Indicates that one entity contains, involves, or incorporates a sacramental rite or practice as part of itself or its activities.
-
D.
recognizesSacrament
Indicates that one entity formally accepts or acknowledges the validity or legitimacy of a particular sacrament associated with another entity.
-
E.
hasCommunion
Indicates that one entity shares or participates in a close, often spiritual or sacramental, union or fellowship with another entity.
- 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_6a01bcd39760819081807a02eb1939d1 |
completed | May 11, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_6a01bc3f1c74819087580e3134affc60 |
completed | May 11, 2026, 11:23 a.m. |
Created at: May 1, 2026, 2:04 a.m.