Triple
T20883664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 2 in Minnesota |
E514215
|
entity |
| Predicate | westernTerminusConnection |
P44831
|
FINISHED |
| Object | U.S. Route 2 in North Dakota |
—
|
NE NERFINISHED |
How this triple was built (3 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: U.S. Route 2 in North Dakota | Statement: [U.S. Route 2 in Minnesota, westernTerminusConnection, U.S. Route 2 in North Dakota]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: U.S. Route 2 in North Dakota Context triple: [U.S. Route 2 in Minnesota, westernTerminusConnection, U.S. Route 2 in North Dakota]
-
A.
U.S. Route 12 in North Dakota
U.S. Route 12 in North Dakota is an east–west U.S. Highway crossing the state’s southwestern region, connecting rural communities and linking Montana to South Dakota.
-
B.
U.S. Route 2 in Minnesota
U.S. Route 2 in Minnesota is a major east–west U.S. Highway crossing northern Minnesota, connecting North Dakota to Wisconsin while serving key regional cities and transportation corridors.
-
C.
U.S. Route 12 in Minnesota
U.S. Route 12 in Minnesota is a major east–west federal highway segment that traverses the southern part of the state, connecting rural communities with the Twin Cities metropolitan area and continuing toward neighboring states.
-
D.
U.S. Route 212 in Minnesota
U.S. Route 212 in Minnesota is a major east–west federal highway that connects rural western parts of the state with the Twin Cities metropolitan area.
-
E.
U.S. Route 23 in North Carolina
U.S. Route 23 in North Carolina is a major north–south highway traversing the state's western region, connecting mountain communities and serving as an important corridor for regional travel and commerce.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: U.S. Route 2 in North Dakota Target entity description: U.S. Route 2 in North Dakota is a major east–west highway crossing the northern part of the state, connecting Montana to Minnesota and serving as a key regional transportation corridor.
-
A.
U.S. Route 12 in North Dakota
U.S. Route 12 in North Dakota is an east–west U.S. Highway crossing the state’s southwestern region, connecting rural communities and linking Montana to South Dakota.
-
B.
U.S. Route 2 in Minnesota
U.S. Route 2 in Minnesota is a major east–west U.S. Highway crossing northern Minnesota, connecting North Dakota to Wisconsin while serving key regional cities and transportation corridors.
-
C.
U.S. Route 12 in Minnesota
U.S. Route 12 in Minnesota is a major east–west federal highway segment that traverses the southern part of the state, connecting rural communities with the Twin Cities metropolitan area and continuing toward neighboring states.
-
D.
U.S. Route 212 in Minnesota
U.S. Route 212 in Minnesota is a major east–west federal highway that connects rural western parts of the state with the Twin Cities metropolitan area.
-
E.
U.S. Route 23 in North Carolina
U.S. Route 23 in North Carolina is a major north–south highway traversing the state's western region, connecting mountain communities and serving as an important corridor for regional travel and commerce.
- F. None of above. chosen
Provenance (2 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c67b03088190be7cbcde8c59509a |
completed | April 21, 2026, 12:36 a.m. |
Created at: April 16, 2026, 12:46 p.m.