Triple
T7142850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matanuska Glacier |
E166489
|
entity |
| Predicate | nearbyHighwayMilepost |
P75083
|
FINISHED |
| Object | around mile 102 of the Glenn Highway |
—
|
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: around mile 102 of the Glenn Highway | Statement: [Matanuska Glacier, nearbyHighwayMilepost, around mile 102 of the Glenn Highway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyHighwayMilepost Context triple: [Matanuska Glacier, nearbyHighwayMilepost, around mile 102 of the Glenn Highway]
-
A.
motorwayJunctionNearby
Indicates that a motorway junction is located close to the referenced entity.
-
B.
nearbyMajorRoad
Indicates that one entity is located close to a significant or heavily used road.
-
C.
nearestInterstateHighway
Indicates that one interstate highway is the closest in distance to a given location or route compared to all other interstate highways.
-
D.
nearestMotorway
Indicates that one entity is the motorway that is geographically closest to the other entity.
-
E.
nearestRoadHead
Indicates that one location is the closest accessible road endpoint (or road access point) to another location.
- 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_69c6888579d481909e05a8d6b81bf733 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e779ace48190be9c33750e60a79e |
completed | March 27, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a213508190a40aca39f9eee7d5 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:45 p.m.