Triple
T1849608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shalosh Regalim |
E41363
|
entity |
| Predicate | includesRitual |
P28133
|
FINISHED |
| Object | pilgrimage to Jerusalem |
—
|
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: pilgrimage to Jerusalem | Statement: [Shalosh Regalim, includesRitual, pilgrimage to Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRitual Context triple: [Shalosh Regalim, includesRitual, pilgrimage to Jerusalem]
-
A.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
B.
appearsInRitual
Indicates that an entity is included, featured, or participates as a component or element within a specific ritual.
-
C.
partOfRitual
Indicates that an action, object, or event is included as a component or step within a larger ritual.
-
D.
containsRite
chosen
Indicates that one entity includes or incorporates a specific rite as part of its structure, content, or practice.
-
E.
hasRitualObject
Indicates that an entity possesses, uses, or is associated with an object specifically employed in a ritual or ceremonial context.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdca6d8819083c66f3a29fd9fd1 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.