Triple
T30969080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | منطقة عرفة |
E789040
|
entity |
| Predicate | timeSpecificRitual |
P77079
|
FINISHED |
| Object | يقف فيها الحجاج يوم 9 ذي الحجة |
—
|
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: يقف فيها الحجاج يوم 9 ذي الحجة | Statement: [منطقة عرفة, timeSpecificRitual, يقف فيها الحجاج يوم 9 ذي الحجة]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSpecificRitual Context triple: [منطقة عرفة, timeSpecificRitual, يقف فيها الحجاج يوم 9 ذي الحجة]
-
A.
mainRitualTime
chosen
Indicates the time at which the primary or central ritual is performed.
-
B.
ritualEvent
Indicates that an event is a ritual or ceremonial occurrence, typically involving prescribed actions, symbols, or practices performed according to tradition or custom.
-
C.
ritualDate
Indicates the specific date on which a ritual or ceremonial event takes place.
-
D.
ritualsDirectedAt
Indicates that certain rituals are performed with a specific entity, object, or target as their intended focus or recipient.
-
E.
initiatesRitual
Indicates that one entity begins or sets in motion a ritual involving one or more other entities.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 8:54 p.m.