Triple
T24306634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocky Mountain Division |
E612552
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | operating division of the Milwaukee Road |
C13555
|
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: operating division of the Milwaukee Road Context triple: [Rocky Mountain Division, instanceOf, operating division of the Milwaukee Road]
-
A.
railroad operating division
chosen
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.
-
B.
historical transit operating division
A historical transit operating division is an organizational unit within a past or legacy public transportation system responsible for managing and coordinating transit services, personnel, and resources within a specific geographic area or operational domain.
-
C.
Chicago 'L' branch
A Chicago 'L' branch is a specific route segment of the Chicago elevated rapid transit system that diverges from a main line to serve particular neighborhoods or corridors.
-
D.
public transport maintenance division
A public transport maintenance division is an organizational unit responsible for inspecting, repairing, and servicing vehicles and infrastructure to ensure the safe, reliable, and efficient operation of a public transportation system.
-
E.
Shawnee division
Shawnee division refers to a specific subgroup or organizational unit associated with the Shawnee people, typically distinguished by geographic location, lineage, or administrative function.
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 1:31 a.m.