Triple
T20558294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Highways in Minnesota |
E504777
|
entity |
| Predicate | includesRoute |
P4374
|
FINISHED |
| Object | U.S. Route 59 in Minnesota |
—
|
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 59 in Minnesota | Statement: [U.S. Highways in Minnesota, includesRoute, U.S. Route 59 in Minnesota]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: U.S. Route 59 in Minnesota Context triple: [U.S. Highways in Minnesota, includesRoute, U.S. Route 59 in Minnesota]
-
A.
U.S. Route 59 in Iowa
U.S. Route 59 in Iowa is a north–south U.S. Highway running through western Iowa, connecting small towns and rural areas between the Missouri and Minnesota state lines.
-
B.
U.S. Highway 52 in Minnesota
U.S. Highway 52 in Minnesota is a major north–south corridor connecting the Twin Cities with Rochester and southeastern Minnesota, serving as an important route for regional travel and commerce.
-
C.
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.
-
D.
U.S. Route 59 in Missouri
U.S. Route 59 in Missouri is a north–south U.S. Highway that runs through the western part of the state, connecting rural communities and regional centers as part of a larger multistate route from Texas to Minnesota.
-
E.
U.S. Highway 61 in Minnesota
U.S. Highway 61 in Minnesota is a major north–south route that follows the Mississippi River and Lake Superior, connecting the Twin Cities to numerous historic river towns and scenic North Shore communities.
- 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 59 in Minnesota Target entity description: U.S. Route 59 in Minnesota is a north–south United States highway that traverses western Minnesota, connecting rural communities and serving as a regional transportation corridor.
-
A.
U.S. Route 59 in Iowa
U.S. Route 59 in Iowa is a north–south U.S. Highway running through western Iowa, connecting small towns and rural areas between the Missouri and Minnesota state lines.
-
B.
U.S. Highway 52 in Minnesota
U.S. Highway 52 in Minnesota is a major north–south corridor connecting the Twin Cities with Rochester and southeastern Minnesota, serving as an important route for regional travel and commerce.
-
C.
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.
-
D.
U.S. Route 59 in Missouri
U.S. Route 59 in Missouri is a north–south U.S. Highway that runs through the western part of the state, connecting rural communities and regional centers as part of a larger multistate route from Texas to Minnesota.
-
E.
U.S. Highway 61 in Minnesota
U.S. Highway 61 in Minnesota is a major north–south route that follows the Mississippi River and Lake Superior, connecting the Twin Cities to numerous historic river towns and scenic North Shore communities.
- 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_69e0b4b6587c8190aee63dc7cff244ea |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a5df84088190848c7eb35564d8f9 |
completed | April 20, 2026, 10:17 p.m. |
Created at: April 16, 2026, 11:38 a.m.