Triple
T21503393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FOCs |
E530535
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rail freight operating company collective term |
C14575
|
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: rail freight operating company collective term Context triple: [FOCs, instanceOf, rail freight operating company collective term]
-
A.
freight railroad company
A freight railroad company is an organization that owns or operates rail infrastructure and rolling stock to transport goods and commodities by train between industrial, commercial, and logistics locations.
-
B.
group of railway companies
chosen
A group of railway companies is an organized association of multiple rail transport operators that collaborate or are collectively managed to provide coordinated rail services, share resources, or pursue common commercial or regulatory interests.
-
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.
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.
rail transport company
A rail transport company is an organization that owns, operates, or manages trains and railway infrastructure to provide freight and/or passenger transportation 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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:24 p.m.