Triple
T8117053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Family Lines System |
E189501
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railroad operating alliance |
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: railroad operating alliance Context triple: [Family Lines System, instanceOf, railroad operating alliance]
-
A.
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.
-
B.
railroad operating division
A railroad operating division is a geographically defined segment of a railway system managed as a unit for train operations, crew assignments, dispatching, and maintenance activities.
-
C.
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.
-
D.
railway holding company
A railway holding company is a parent corporation that owns and controls one or more railway operating or infrastructure companies, managing their strategic direction and financial interests without necessarily running day-to-day train operations itself.
-
E.
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.
- 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_69ca82baad008190ab2859712b9b1607 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:33 p.m.