Triple
T29953670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Eastern Area |
E760837
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional division of a railway company |
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: regional division of a railway company Context triple: [North Eastern Area, instanceOf, regional division of a railway company]
-
A.
division of a private railway company
A division of a private railway company is an organizational unit within the company responsible for managing specific operational, geographic, or functional aspects of its rail services and related activities.
-
B.
railroad district
A railroad district is a designated geographic or administrative area organized around railway infrastructure, operations, and services, often encompassing tracks, stations, yards, and related facilities.
-
C.
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.
-
D.
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.
-
E.
region of British Railways
A region of British Railways is a large administrative and operational division of the national rail network, responsible for managing railway services, infrastructure, and staff within a defined geographic area of Great Britain.
- 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:26 p.m.