Triple
T25547397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kantishna |
E640346
|
entity |
| Predicate | roadMileMarker |
P20523
|
FINISHED |
| Object | approximately mile 92 of Denali Park Road |
—
|
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 mile 92 of Denali Park Road | Statement: [Kantishna, roadMileMarker, approximately mile 92 of Denali Park Road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadMileMarker Context triple: [Kantishna, roadMileMarker, approximately mile 92 of Denali Park Road]
-
A.
approximateMileMarker
chosen
Indicates an estimated or not precisely measured position along a route expressed in miles.
-
B.
riverMilepost
Indicates the specific distance or position along a river, measured in miles from a defined starting point.
-
C.
nearbyHighwayMilepost
Indicates that one entity is located close to a specific highway milepost associated with another entity.
-
D.
trailMilepostOn
Indicates that a specific milepost is physically located on and associated with a particular trail segment or trail route.
-
E.
blueRidgeParkwayMilepost
Indicates a specific location or reference point identified by its milepost number along the Blue Ridge Parkway.
- 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_69e75dc101a881909fd33b02174e9768 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8992ce881909b95d520f580e231 |
completed | May 2, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 3:35 p.m.