Triple
T34658909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barquinha |
E890053
|
entity |
| Predicate | usesSubstanceAsSacrament |
P7392
|
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, usesSubstanceAsSacrament, ayahuasca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSubstanceAsSacrament Context triple: [Barquinha, usesSubstanceAsSacrament, ayahuasca]
-
A.
sacramentalUseOf
chosen
Indicates the use of something as a sacrament or within a sacramental religious rite or practice.
-
B.
formOfSacrament
Indicates that one entity is a specific liturgical or ritual form in which a sacrament is administered or expressed.
-
C.
sacramentalSign
Indicates that one entity functions as a visible, ritual sign that conveys or symbolizes a sacred or divine reality in relation to another entity.
-
D.
recognizesSacrament
Indicates that one entity formally accepts or acknowledges the validity or legitimacy of a particular sacrament associated with another entity.
-
E.
coreSacraments
Indicates that the specified religious rites are recognized as the fundamental or primary sacraments within a given religious tradition.
- 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_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 1, 2026, 2:04 a.m.