Triple
T9362764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nirtzah |
E225319
|
entity |
| Predicate | positionInRitual |
P26551
|
FINISHED |
| Object | concluding section of the Haggadah |
—
|
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: concluding section of the Haggadah | Statement: [Nirtzah, positionInRitual, concluding section of the Haggadah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInRitual Context triple: [Nirtzah, positionInRitual, concluding section of the Haggadah]
-
A.
appearsInRitual
Indicates that an entity is included, featured, or participates as a component or element within a specific ritual.
-
B.
roleInRitual
Indicates the specific function, position, or responsibility an entity holds within a particular ritual or ceremonial activity.
-
C.
partOfRitual
chosen
Indicates that an action, object, or event is included as a component or step within a larger ritual.
-
D.
positionInTemple
Indicates the specific location or role an entity occupies within a temple.
-
E.
positionOnPaganRituals
Indicates a stance or viewpoint that an entity holds regarding the practice, acceptability, or interpretation of pagan rituals.
- 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_69ca842bdd648190904131d58620d448 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd503ca7308190818f27f1faf94a53 |
completed | April 1, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69cc7a6abb8c81908c7a2f4ee92cc949 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:42 p.m.