Triple
T30766986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Central Pacific and Mexican Railway |
E783399
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railroad enterprise |
C9409
|
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 enterprise Context triple: [South Central Pacific and Mexican Railway, instanceOf, railroad enterprise]
-
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.
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.
-
C.
rail transport company
chosen
A rail transport company is an organization that owns, operates, or manages trains and railway infrastructure to provide freight and/or passenger transportation services.
-
D.
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.
-
E.
railway construction company
A railway construction company is an organization that plans, designs, and builds railway infrastructure, including tracks, stations, bridges, and related systems, often coordinating engineering, procurement, and project management activities.
- 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_69f224b047f48190b4f5efeb7ee97b37 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:40 p.m.