Triple
T20511400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 75 Business Loop (nearby via Dayton) |
E503571
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | highway business loop |
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: highway business loop Context triple: [Interstate 75 Business Loop (nearby via Dayton), instanceOf, highway business loop]
-
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 loop
A highway loop is a circular or semi-circular roadway segment that connects different parts of a highway system, allowing vehicles to change direction or access intersecting routes without stopping.
-
C.
highway
A highway is a major public road designed for high-speed, long-distance vehicular travel, typically featuring multiple lanes, limited access points, and safety infrastructure.
-
D.
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.
-
E.
highway segment
A highway segment is a continuous portion of a highway between two defined endpoints, such as interchanges, intersections, or mile markers, characterized by consistent physical and operational attributes.
- 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.