Triple
T18242636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hennepin County Regional Railroad Authority |
E436857
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional railroad authority |
C6404
|
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: regional railroad authority Context triple: [Hennepin County Regional Railroad Authority, instanceOf, regional railroad authority]
-
A.
state-owned railroad
A state-owned railroad is a railway system owned and operated by a government entity, providing rail transport services as a public enterprise.
-
B.
national railway company
A national railway company is a state-owned or state-controlled organization responsible for operating and managing a country's primary passenger and freight rail transport services and infrastructure.
-
C.
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.
-
D.
transport infrastructure operator
chosen
A transport infrastructure operator is an entity responsible for managing, maintaining, and regulating transportation networks and facilities such as roads, railways, ports, or airports to ensure safe and efficient movement of people and goods.
-
E.
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.
- 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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:33 a.m.