Triple
T14937464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Railway (Russia) |
E372432
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway division of Russian Railways |
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: railway division of Russian Railways Context triple: [Northern Railway (Russia), instanceOf, railway division of Russian Railways]
-
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.
railway company of Russia
A railway company of Russia is an organization that owns, operates, or manages rail transport infrastructure and services within the Russian Federation, including passenger and freight operations.
-
C.
public railway
A public railway is a government- or publicly-owned rail transport system that provides scheduled passenger and/or freight services accessible to the general population, typically operating on standardized tracks and infrastructure.
-
D.
private railway company
A private railway company is a non-governmental business entity that owns, operates, or manages rail transport services for passengers and/or freight, typically for profit under regulatory oversight.
-
E.
zone of Indian Railways
A zone of Indian Railways is a major administrative and operational division that oversees railway infrastructure, train operations, and services within a defined geographic region of India’s rail network.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:37 a.m.