Triple
T27916012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 95 in Jacksonville |
E706073
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interstate highway corridor |
C527
|
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: interstate highway corridor Context triple: [Interstate 95 in Jacksonville, instanceOf, interstate highway corridor]
-
A.
road transportation corridor
A road transportation corridor is a designated linear area of land that accommodates one or more roadways and associated infrastructure to enable the efficient movement of vehicles, goods, and people between key origins and destinations.
-
B.
Interstate Highway
chosen
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.
-
C.
transport corridor
A transport corridor is a designated route or geographic band that concentrates and connects major transportation infrastructure—such as roads, railways, ports, and logistics hubs—to facilitate efficient movement of people and goods between key locations.
-
D.
Interstate business loop
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.
-
E.
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.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 6:53 p.m.