Triple
T25547568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eielson Visitor Center |
E640350
|
entity |
| Predicate | locatedAtMile |
P2409
|
FINISHED |
| Object | Mile 66 of Denali Park Road |
—
|
NE NERFINISHED |
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: Mile 66 of Denali Park Road | Statement: [Eielson Visitor Center, locatedAtMile, Mile 66 of Denali Park Road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAtMile Context triple: [Eielson Visitor Center, locatedAtMile, Mile 66 of Denali Park Road]
-
A.
approximateMileMarker
Indicates an estimated or not precisely measured position along a route expressed in miles.
-
B.
locatedAlong
chosen
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
-
C.
meterLocation
Indicates the physical placement or position of a meter relative to the object or environment it is associated with.
-
D.
locatedOnRouteTo
Indicates that one entity lies along the path or course taken when traveling from a starting point to a specified destination.
-
E.
approximateLengthInMiles
Indicates the estimated distance or extent of something measured in miles.
- 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_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 21, 2026, 3:35 p.m.