Triple
T25992886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cantwell, Alaska |
E646405
|
entity |
| Predicate | distanceToDenaliNationalParkEntrance |
P71581
|
FINISHED |
| Object | approximately 27 miles |
—
|
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 27 miles | Statement: [Cantwell, Alaska, distanceToDenaliNationalParkEntrance, approximately 27 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToDenaliNationalParkEntrance Context triple: [Cantwell, Alaska, distanceToDenaliNationalParkEntrance, approximately 27 miles]
-
A.
distanceToDenali
chosen
Indicates the measured or estimated spatial distance between a given entity and Denali.
-
B.
distanceToGlacierNationalPark
Indicates the measured or estimated spatial distance between a given entity’s location and Glacier National Park.
-
C.
relativeLocationToDenali
Indicates the spatial position or orientation of something in relation to Denali’s location.
-
D.
distanceToWitney
Indicates the spatial distance between an entity and the location Witney.
-
E.
distanceToSequoiaNationalParkEntrance
Indicates the physical distance between a given location and the entrance of Sequoia National Park.
- 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_69e77e88cb8481908da31d4a00661f55 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: April 22, 2026, 8:57 a.m.