Triple
T15065730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delhi–Mumbai Industrial Corridor region |
E379750
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planned economic corridor |
C25151
|
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: planned economic corridor Context triple: [Delhi–Mumbai Industrial Corridor region, instanceOf, planned economic corridor]
-
A.
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.
-
B.
trade and transportation corridor initiative
chosen
A trade and transportation corridor initiative is a coordinated program to develop and optimize key routes, infrastructure, and policies that facilitate efficient movement of goods and people across regions or borders.
-
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.
freight rail corridor
A freight rail corridor is a designated railway route primarily used for the efficient, high-capacity movement of goods and cargo between industrial, commercial, and logistics hubs.
-
E.
development corridor
A development corridor is a strategically planned geographic area, often aligned along major transportation routes, where concentrated investment in infrastructure, industry, and services is used to stimulate economic growth and regional integration.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:02 a.m.