Triple
T25547599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eielson Visitor Center |
E640350
|
entity |
| Predicate | distanceFromEntranceArea |
P115067
|
FINISHED |
| Object | approximately 66 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 66 miles | Statement: [Eielson Visitor Center, distanceFromEntranceArea, approximately 66 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromEntranceArea Context triple: [Eielson Visitor Center, distanceFromEntranceArea, approximately 66 miles]
-
A.
distanceToTheEntrance
chosen
Indicates the spatial distance between a given entity and the entrance of a specified place or structure.
-
B.
nearestEntrance
Indicates that one entrance is the closest access point to a given location or entity compared to all other possible entrances.
-
C.
distanceFromTerminus
Indicates the measured distance of an entity from a defined endpoint or terminus along a route, path, or sequence.
-
D.
distanceFromBath
Indicates the spatial distance between an entity and a specified bath or bathing facility.
-
E.
distanceFromStation
Indicates the measured spatial separation between an entity and a specified station.
- 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_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 21, 2026, 3:35 p.m.