Triple
T7532416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hajj al-Ifrad |
E178056
|
entity |
| Predicate | startRite |
P45952
|
FINISHED |
| Object | intention (niyyah) for Hajj only |
—
|
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: intention (niyyah) for Hajj only | Statement: [Hajj al-Ifrad, startRite, intention (niyyah) for Hajj only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startRite Context triple: [Hajj al-Ifrad, startRite, intention (niyyah) for Hajj only]
-
A.
starterType
Indicates the classification or category of a starter (e.g., initial component, opening item, or first phase) associated with an entity or process.
-
B.
startingGuard
Indicates that an entity serves as the primary or first-choice guard in a lineup, formation, or configuration.
-
C.
startPoint
Indicates the initial location or position from which an object, path, or action begins.
-
D.
mainRite
chosen
Indicates that one ritual, ceremony, or rite is the primary or central rite associated with a given context, entity, or event.
-
E.
startRule
Indicates that a particular rule is the initial or entry rule from which a process, system, or evaluation begins.
- 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_69c69f2acdbc8190b5a8320168c1d0ba |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f84753fc81908bee2013004ef5fb |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:47 p.m.