Triple
T2485142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shanghai–Wuhan–Chengdu High-Speed Railway |
E55908
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-speed railway corridor |
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: high-speed railway corridor Context triple: [Shanghai–Wuhan–Chengdu High-Speed Railway, instanceOf, high-speed railway corridor]
-
A.
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.
-
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.
rapid transit line segment
A rapid transit line segment is a contiguous portion of a rapid transit route between two defined points (such as stations, junctions, or terminals) that carries high-frequency, high-capacity passenger rail service.
-
D.
road transportation corridor
A road transportation corridor is a designated linear area of land that accommodates one or more roadways and associated infrastructure to enable the efficient movement of vehicles, goods, and people between key origins and destinations.
-
E.
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.
- 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_69ab49e670a88190b928e08302381710 |
completed | March 6, 2026, 9:40 p.m. |
Created at: March 6, 2026, 9:45 p.m.