Triple
T31156232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riyadh–Qurayyat passenger line |
E794214
|
entity |
| Predicate | travelTimeRiyadhToQurayyat |
P173765
|
FINISHED |
| Object | approximately 12 hours |
—
|
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: approximately 12 hours | Statement: [Riyadh–Qurayyat passenger line, travelTimeRiyadhToQurayyat, approximately 12 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelTimeRiyadhToQurayyat Context triple: [Riyadh–Qurayyat passenger line, travelTimeRiyadhToQurayyat, approximately 12 hours]
-
A.
travelTimeMeccaMedina
Indicates the duration or time required to travel between Mecca and Medina.
-
B.
distanceFromRiyadh
Indicates the measured spatial distance between a given entity’s location and the city of Riyadh.
-
C.
distanceFromJeddah
Indicates the measured spatial distance between a given entity and the location of Jeddah.
-
D.
distanceToNasiriyah
Indicates the spatial distance between a given entity and the location of Nasiriyah.
-
E.
distanceFromDoha
Indicates the spatial distance between a given location or entity and the city of Doha.
- 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_69f224d504908190b01278dcb7fc3fa7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6ba1733408190af579d93a7946508 |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: April 29, 2026, 9:07 p.m.