Triple
T24679798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BNSF Railway facilities in Pittsburg, California |
E611095
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | freight rail infrastructure |
C3584
|
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 infrastructure Context triple: [BNSF Railway facilities in Pittsburg, California, instanceOf, freight rail infrastructure]
-
A.
rail transportation infrastructure
chosen
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
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.
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.
-
E.
commuter rail infrastructure
Commuter rail infrastructure comprises the physical and operational systems—such as tracks, stations, signaling, power, and maintenance facilities—designed to support frequent, reliable passenger train service between suburbs and urban centers.
- 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_69e2c4d5c2dc8190ac857dea25ec6ce9 |
completed | April 17, 2026, 11:40 p.m. |
Created at: April 18, 2026, 3:08 a.m.