Triple
T4561557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USRA standard freight car designs |
E121802
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States railroad standard |
C17191
|
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: United States railroad standard Context triple: [USRA standard freight car designs, instanceOf, United States railroad standard]
-
A.
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.
-
B.
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.
-
C.
Class I railroad
A Class I railroad is a large freight railroad company that exceeds a specific annual revenue threshold set by transportation regulators, distinguishing it from smaller regional and local rail carriers.
-
D.
common carrier railroad
A common carrier railroad is a rail transport company that offers freight and/or passenger services to the general public under legal obligation to serve all customers without discrimination, according to published rates and schedules.
-
E.
standardized rail interface
A standardized rail interface is a uniform physical and electrical connection system that allows different rail vehicles, components, or infrastructure elements to interoperate safely and efficiently across multiple networks or manufacturers.
- F. None of above. chosen
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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 1:09 p.m.