Triple
T37254568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalyan–Karjat line |
E924089
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | main line railway corridor |
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: main line railway corridor Context triple: [Kalyan–Karjat line, instanceOf, main line railway corridor]
-
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.
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.
-
C.
railroad line
A railroad line is a fixed route consisting of tracks and associated infrastructure over which trains operate to transport passengers or freight between locations.
-
D.
commuter rail line
A commuter rail line is a passenger train service that operates on fixed tracks and schedules to connect suburban or outlying areas with a central city, primarily serving daily work and school commuters.
-
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_69f76eaabb4c819093b751b139dad551 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:15 p.m.