Triple
T30819317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Rukn al-Iraqi |
E784872
|
entity |
| Predicate | isPartOfRitualContext |
P26551
|
FINISHED |
| Object | Hajj |
—
|
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: Hajj | Statement: [al-Rukn al-Iraqi, isPartOfRitualContext, Hajj]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfRitualContext Context triple: [al-Rukn al-Iraqi, isPartOfRitualContext, Hajj]
-
A.
hasRitualContext
Indicates that one entity is associated with, or occurs within, a ritual or ceremonial context in relation to another entity.
-
B.
indicatesRitualStatus
Indicates that something serves as a sign or marker of an entity’s status or role within a ritual context.
-
C.
hasRitualSetting
Indicates that an entity is associated with a specific ritual context or environment in which it is performed, observed, or situated.
-
D.
partOfRitual
chosen
Indicates that an action, object, or event is included as a component or step within a larger ritual.
-
E.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: April 29, 2026, 8:44 p.m.