Triple
T11954193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teller, Alaska |
E284507
|
entity |
| Predicate | distanceToNomeByRoad |
P102449
|
FINISHED |
| Object | approximately 72 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 72 miles | Statement: [Teller, Alaska, distanceToNomeByRoad, approximately 72 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToNomeByRoad Context triple: [Teller, Alaska, distanceToNomeByRoad, approximately 72 miles]
-
A.
approximateRouteLength
Indicates the estimated total distance or length of a given route, rather than its exact measured value.
-
B.
isRemoteByRoad
Indicates that one location is difficult or time-consuming to reach from another when traveling by road.
-
C.
flightDistance
Indicates the measured distance covered by a flight between its origin and destination.
-
D.
trekDistanceFromRoadHead
Indicates the distance one must trek from the road head (road access point) to reach a specified location.
-
E.
distanceToOttawaByRoad
Indicates the length of the travel route between a place and Ottawa when moving along the road network rather than in a straight line.
- F. None of above. chosen
Provenance (4 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90365da288190a132703df563de23 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8dd0ba0f88190b7d5e358c27ca184 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:45 p.m.