Triple
T6308318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Pacific mainline routes |
E141434
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | freight rail corridor system |
C3454
|
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 rail corridor system Context triple: [Union Pacific mainline routes, instanceOf, freight rail corridor system]
-
A.
freight rail corridor
chosen
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.
-
B.
freight railroad network
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.
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.
-
D.
transport corridor
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.
-
E.
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.
- 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_69c008d00efc8190a36c05b4b4a3bf4b |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:28 p.m.