Triple
T19564917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haines Junction, Yukon |
E489553
|
entity |
| Predicate | distanceToAlaskaBorder |
P56658
|
FINISHED |
| Object | approximately 200 km |
—
|
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 200 km | Statement: [Haines Junction, Yukon, distanceToAlaskaBorder, approximately 200 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToAlaskaBorder Context triple: [Haines Junction, Yukon, distanceToAlaskaBorder, approximately 200 km]
-
A.
distanceToAlaskaApproxKm
chosen
Indicates the approximate distance, measured in kilometers, between a given entity’s location and the state of Alaska.
-
B.
distanceFromAnchorage
Indicates the measured distance between a given location or object and Anchorage.
-
C.
approximateDistanceFromAnchorage
Indicates the estimated spatial distance between a given entity and Anchorage, rather than an exact measured value.
-
D.
distanceToAlbertaBorder
Indicates the measured spatial distance between a given location and the border of Alberta.
-
E.
distanceToCanadianBorder
Indicates the measured or estimated spatial distance between a given location and the nearest point on the Canadian national border.
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63f76b220819096e668534c6bac67 |
completed | April 20, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:42 p.m.