Triple
T4379490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ExpressRail system |
E99093
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | freight transportation infrastructure |
C2652
|
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: freight transportation infrastructure Context triple: [ExpressRail system, instanceOf, freight transportation infrastructure]
-
A.
rail transportation infrastructure
Rail transportation infrastructure encompasses the physical and organizational systems—such as tracks, stations, signaling, power supply, and related facilities—required to support the safe and efficient movement of trains and rail-based services.
-
B.
freight railroad network
chosen
A freight railroad network is an interconnected system of rail lines, terminals, and supporting infrastructure designed to transport goods and raw materials efficiently between industrial, commercial, and logistical hubs.
-
C.
transport infrastructure network
A transport infrastructure network is an interconnected system of physical routes and facilities—such as roads, railways, ports, and airports—designed to enable the efficient movement of people and goods across regions.
-
D.
freight railroad
A freight railroad is a rail transport system dedicated to moving goods and commodities—such as raw materials, manufactured products, and containers—using freight trains over a network of tracks.
-
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_69b3454ea8f48190a49c2436624d6ef6 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:18 p.m.