Triple
T26595328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qarin |
E667474
|
entity |
| Predicate | ihramIntention |
P161587
|
FINISHED |
| Object | for both Hajj and Umrah together |
—
|
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: for both Hajj and Umrah together | Statement: [Qarin, ihramIntention, for both Hajj and Umrah together]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ihramIntention Context triple: [Qarin, ihramIntention, for both Hajj and Umrah together]
-
A.
ihramType
Indicates the specific form or category of ihram (pilgrimage state) associated with a given pilgrimage act or person.
-
B.
ihramStart
Indicates the initiation of the state of ihram, marking when an individual formally begins the ritual consecration for pilgrimage.
-
C.
ihramState
Indicates that an entity is currently in the consecrated state of ihram required for performing certain Islamic pilgrimage rites.
-
D.
ihramChange
Indicates a change in a person’s state of ihram, such as entering into, modifying, or exiting the ritual consecration status.
-
E.
ihramDuration
Indicates the length of time for which a person remains in the state of ihram during a pilgrimage.
- F. None of above. chosen
Provenance (4 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61ad613608190855de13501a86007 |
completed | May 2, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f61a16b7848190bf20d2be7e5a16c1 |
completed | May 2, 2026, 3:36 p.m. |
Created at: April 27, 2026, 2:10 a.m.