Triple
T22974620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Highways in Indiana |
E571279
|
entity |
| Predicate | hasRoute |
P4374
|
FINISHED |
| Object | U.S. Route 35 in Indiana |
—
|
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 35 in Indiana | Statement: [U.S. Highways in Indiana, hasRoute, U.S. Route 35 in Indiana]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: U.S. Route 35 in Indiana Context triple: [U.S. Highways in Indiana, hasRoute, U.S. Route 35 in Indiana]
-
A.
U.S. Route 33 in Indiana
U.S. Route 33 in Indiana is a major federal highway that traverses the state, connecting several key cities and serving as an important regional transportation corridor.
-
B.
U.S. Route 35 in Ohio
U.S. Route 35 in Ohio is a major east–west U.S. highway that connects the Dayton area to the West Virginia state line, serving as an important regional corridor across southern Ohio.
-
C.
U.S. Route 31 in Indiana
U.S. Route 31 in Indiana is a major north–south highway that connects key cities such as Indianapolis and South Bend, serving as an important regional transportation corridor.
-
D.
U.S. Route 30 in Indiana
U.S. Route 30 in Indiana is a major east–west U.S. Highway that serves as a key transportation corridor across northern Indiana, connecting cities such as Fort Wayne and Valparaiso.
-
E.
U.S. Route 40 in Indiana
U.S. Route 40 in Indiana is the segment of the historic east–west U.S. Highway that crosses the state, largely following the path of the National Road and connecting major communities between the Ohio and Illinois borders.
- 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 35 in Indiana Target entity description: U.S. Route 35 in Indiana is a major north–south U.S. Highway that connects rural communities and regional cities across the state, serving as an important corridor for local and through traffic.
-
A.
U.S. Route 33 in Indiana
U.S. Route 33 in Indiana is a major federal highway that traverses the state, connecting several key cities and serving as an important regional transportation corridor.
-
B.
U.S. Route 35 in Ohio
U.S. Route 35 in Ohio is a major east–west U.S. highway that connects the Dayton area to the West Virginia state line, serving as an important regional corridor across southern Ohio.
-
C.
U.S. Route 31 in Indiana
U.S. Route 31 in Indiana is a major north–south highway that connects key cities such as Indianapolis and South Bend, serving as an important regional transportation corridor.
-
D.
U.S. Route 30 in Indiana
U.S. Route 30 in Indiana is a major east–west U.S. Highway that serves as a key transportation corridor across northern Indiana, connecting cities such as Fort Wayne and Valparaiso.
-
E.
U.S. Route 40 in Indiana
U.S. Route 40 in Indiana is the segment of the historic east–west U.S. Highway that crosses the state, largely following the path of the National Road and connecting major communities between the Ohio and Illinois borders.
- 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_69e245b2c6548190a0e4c7f2f7df2d48 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182350b448190a34e5fa0167fd964 |
completed | April 29, 2026, 3:59 a.m. |
Created at: April 17, 2026, 3:48 p.m.