Triple
T29563029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medina–Jeddah highway |
E750086
|
entity |
| Predicate | roleInUmrah |
P198919
|
FINISHED |
| Object | frequently used by Umrah pilgrims |
—
|
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: frequently used by Umrah pilgrims | Statement: [Medina–Jeddah highway, roleInUmrah, frequently used by Umrah pilgrims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInUmrah Context triple: [Medina–Jeddah highway, roleInUmrah, frequently used by Umrah pilgrims]
-
A.
roleInHajj
Indicates the specific function, duty, or position an entity holds within the context of performing or organizing the Hajj pilgrimage.
-
B.
roleInMecca
Indicates that an entity holds or performs a specific role, function, or position in the context of Mecca.
-
C.
performsUmrahTawaf
Indicates that an entity carries out the ritual circumambulation (tawaf) around the Kaaba as part of performing Umrah.
-
D.
umrahIncluded
Indicates that the arrangement, package, or service includes the performance of Umrah as part of what is provided.
-
E.
roleInMosque
Indicates that an entity holds or performs a specific role, function, or position within a mosque.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69ff14d596e88190be5263b7f96a96cd |
completed | May 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69ff13f0208081909369aeb3b77a6b1f |
completed | May 9, 2026, 11:01 a.m. |
| PDg | Predicate description generation | batch_69ff14d4dfc48190bc9fba2384988a98 |
completed | May 9, 2026, 11:04 a.m. |
Created at: April 28, 2026, 5:21 p.m.