Triple
T33236422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indo-Nepal railway corridor |
E850840
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cross-border railway corridor |
C20620
|
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: cross-border railway corridor Context triple: [Indo-Nepal railway corridor, instanceOf, cross-border railway corridor]
-
A.
international railway
chosen
An international railway is a rail transport system or route that connects and facilitates the movement of passengers and freight between two or more countries across their national borders.
-
B.
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.
-
C.
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.
-
D.
road–rail border crossing
A road–rail border crossing is a designated point at an international boundary where both road and railway transport routes intersect or pass through, enabling the controlled movement of vehicles, trains, goods, and passengers between neighboring countries.
-
E.
rail border crossing
A rail border crossing is a designated point where railway lines intersect an international boundary, enabling the controlled movement of trains, cargo, and passengers between countries.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:31 a.m.