Triple
T34658869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | União do Vegetal |
E890052
|
entity |
| Predicate | hasCentralRitual |
P111635
|
FINISHED |
| Object | ayahuasca ceremony |
—
|
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 ceremony | Statement: [União do Vegetal, hasCentralRitual, ayahuasca ceremony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralRitual Context triple: [União do Vegetal, hasCentralRitual, ayahuasca ceremony]
-
A.
ritualCentersOn
chosen
Indicates that a ritual is primarily focused on, organized around, or thematically centered on a particular entity, object, or concept.
-
B.
hasRituals
Indicates that one entity performs, observes, or is associated with specific rituals in relation to another entity or context.
-
C.
mainLocationOfRituals
Indicates that a place serves as the primary setting where a group's rituals are regularly performed.
-
D.
hasRitualCalendar
Indicates that an entity maintains or is associated with a structured schedule of ritual or ceremonial events.
-
E.
ritualsDirectedAt
Indicates that certain rituals are performed with a specific entity, object, or target as their intended focus or recipient.
- 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_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 1, 2026, 2:04 a.m.