Triple
T34857279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trans-Siberian Railway region (southern flank proximity) |
E1004760
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway corridor region |
C2952
|
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 region Context triple: [Trans-Siberian Railway region (southern flank proximity), instanceOf, railway corridor region]
-
A.
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.
-
B.
transport corridor
chosen
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.
transport corridor segment
A transport corridor segment is a defined linear portion of a transportation route (such as a road, rail line, or shipping lane) characterized by consistent physical, operational, and regulatory attributes used for planning, management, and analysis.
-
E.
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.
- 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.