Triple
T2807935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salang Pass |
E54097
|
entity |
| Predicate | previousMainRoute |
P18010
|
FINISHED |
| Object | Khyber Pass via Pakistan |
—
|
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: Khyber Pass via Pakistan | Statement: [Salang Pass, previousMainRoute, Khyber Pass via Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousMainRoute Context triple: [Salang Pass, previousMainRoute, Khyber Pass via Pakistan]
-
A.
previousRoute
chosen
Indicates that one route directly precedes another in an ordered sequence of routes.
-
B.
primaryRoute
Indicates that one route is designated as the main or preferred path among possible alternatives between locations.
-
C.
previousHome
Indicates that one entity served as a former or prior residence or home of another entity.
-
D.
nextRoute
Indicates that one route directly follows another in a defined sequence or ordering of routes.
-
E.
parentRoute
Indicates that one route serves as the direct hierarchical ancestor or container of another route within a routing structure.
- 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_69ab49dcee188190b5c6eca9ae9e3469 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde2fdcf88190a52e515c166ea8f7 |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd059f308190853191f6ffe2bc6f |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.