Triple
T29813280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Orleans–Jackson corridor |
E757029
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional travel corridor |
C2952
|
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: regional travel corridor Context triple: [New Orleans–Jackson corridor, instanceOf, regional travel corridor]
-
A.
transport corridor
chosen
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.
-
B.
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.
-
C.
Indigenous travel corridor
An Indigenous travel corridor is a traditional route or network of pathways used by Indigenous peoples for movement, trade, cultural exchange, and connection across their ancestral lands.
-
D.
population corridor
A population corridor is a geographic or infrastructural pathway that facilitates the movement, interaction, and distribution of people between distinct population centers.
-
E.
planned transit corridor
A planned transit corridor is a designated route or area reserved for future development of public transportation infrastructure, such as bus rapid transit or rail lines, to guide growth and improve regional mobility.
- 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_69f2245701c88190ad42415a0956c4ed |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:25 p.m.