Triple
T20511401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 75 Business Loop (nearby via Dayton) |
E503571
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | business route of Interstate 75 |
C22170
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: business route of Interstate 75 Context triple: [Interstate 75 Business Loop (nearby via Dayton), instanceOf, business route of Interstate 75]
-
A.
Interstate business loop
chosen
An Interstate business loop is a special route that departs from an Interstate Highway to pass through the downtown or commercial center of a nearby city before reconnecting with the same Interstate.
-
B.
highway route
A highway route is a designated path along interconnected roads or highways, identified by a specific number or name, that guides long-distance vehicular travel between regions or destinations.
-
C.
Interstate Highway
An Interstate Highway is a high-capacity, limited-access roadway that forms part of a nationwide network designed to support efficient long-distance and high-speed vehicular travel between major cities and regions.
-
D.
U.S. Highway business route
A U.S. Highway business route is a special alignment of a U.S. Highway that diverts from the main route to pass through the downtown or commercial center of a city or town, providing local access to businesses and services.
-
E.
Farm to Market Road
A Farm to Market Road is a rural roadway designed to connect agricultural areas and farms with nearby towns, markets, and major transportation routes to facilitate the movement of goods and people.
- F. None of above.
Provenance (1 batch)
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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:36 a.m.