Triple
T3865579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khunjerab Pass |
E91843
|
entity |
| Predicate | roadAccessFromPakistan |
P22549
|
FINISHED |
| Object | via Karakoram Highway from Gilgit and Hunza |
—
|
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: via Karakoram Highway from Gilgit and Hunza | Statement: [Khunjerab Pass, roadAccessFromPakistan, via Karakoram Highway from Gilgit and Hunza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadAccessFromPakistan Context triple: [Khunjerab Pass, roadAccessFromPakistan, via Karakoram Highway from Gilgit and Hunza]
-
A.
roadAccessFrom
chosen
Indicates that one location can be reached from another via a usable road connection.
-
B.
roadAccessVia
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
-
C.
isRoadAccessible
Indicates that a road can be safely and legally used or traversed under the current conditions.
-
D.
roadAccessSeason
Indicates the time of year or season during which road access to a place or area is available or permitted.
-
E.
transportModeAccess
Indicates that one entity has the ability or permission to use, reach, or be served by a particular mode of transportation.
- 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec3a253c81909df7dc0422ff7989 |
completed | March 9, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69aee754dddc8190936e1f9c40a770db |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.