Triple
T35057236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yasna ceremony |
E1011500
|
entity |
| Predicate | includesRitualAction |
P29760
|
FINISHED |
| Object | libation |
—
|
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: libation | Statement: [Yasna ceremony, includesRitualAction, libation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRitualAction Context triple: [Yasna ceremony, includesRitualAction, libation]
-
A.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
B.
appearsInRitual
chosen
Indicates that an entity is included, featured, or participates as a component or element within a specific ritual.
-
C.
hasRituals
Indicates that one entity performs, observes, or is associated with specific rituals in relation to another entity or context.
-
D.
hasRitualRule
Indicates that an entity is governed by, or associated with, a specific ritual rule or prescribed ceremonial guideline.
-
E.
hasRitualSetting
Indicates that an entity is associated with a specific ritual context or environment in which it is performed, observed, or situated.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.