Triple
T25682894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chennai–Tiruchirappalli line |
E643988
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | electrified railway corridor |
C12520
|
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: electrified railway corridor Context triple: [Chennai–Tiruchirappalli line, instanceOf, electrified railway corridor]
-
A.
electrified railway
chosen
An electrified railway is a rail transport system in which trains receive power from external electrical sources, such as overhead lines or third rails, instead of relying on onboard fuel.
-
B.
electrified railway operation
Electrified railway operation is the management and control of train services powered by electrical energy supplied through overhead lines or third rails, encompassing infrastructure, rolling stock, power systems, and operational procedures to ensure safe, efficient, and reliable transport.
-
C.
third rail electrification system
A third rail electrification system is a method of providing electric power to trains via an additional rail mounted alongside or between the running rails, from which current is collected by contact shoes on the train.
-
D.
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.
-
E.
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.
- 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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 8:03 p.m.