Triple
T19025443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delhi–Kolkata main line (via Lucknow and Mughalsarai, NR portion) |
E465597
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway corridor segment |
C3787
|
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: railway corridor segment Context triple: [Delhi–Kolkata main line (via Lucknow and Mughalsarai, NR portion), instanceOf, railway corridor segment]
-
A.
railway line
chosen
A railway line is a fixed transportation route consisting of tracks, signaling, and related infrastructure along which trains operate between defined locations.
-
B.
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.
-
C.
suburban railway corridor
A suburban railway corridor is a dedicated rail route connecting city centers with surrounding residential suburbs, designed to support frequent, high-capacity commuter train services.
-
D.
underground rail corridor
An underground rail corridor is a subsurface passageway engineered to safely guide trains between stations, housing tracks, utilities, and supporting infrastructure while minimizing surface disruption.
-
E.
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.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:02 p.m.