Triple
T5130850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deadhorse, Alaska |
E115694
|
entity |
| Predicate | roadTerminus |
P22217
|
FINISHED |
| Object | northern terminus of the Dalton Highway |
—
|
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: northern terminus of the Dalton Highway | Statement: [Deadhorse, Alaska, roadTerminus, northern terminus of the Dalton Highway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadTerminus Context triple: [Deadhorse, Alaska, roadTerminus, northern terminus of the Dalton Highway]
-
A.
roadTerminusOf
chosen
Indicates that a road ends at, or has its terminal point at, the referenced location or route.
-
B.
roadJunctionIncludes
Indicates that a road junction spatially contains or encompasses a specific road segment or related roadway element as part of its structure.
-
C.
roadNetworkHubOf
Indicates that one location functions as a central node or hub within the road network relative to another location or area.
-
D.
roadServed
Indicates that a road is provided with necessary services or infrastructure support by a responsible entity.
-
E.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
- 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_69bd444426bc819099ccd23f141e22aa |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7fef2e8c8190982dd67f50295ada |
completed | March 20, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69bd77ac2fc48190abeebb003a82384c |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:42 p.m.