Triple
T32537588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ER |
E831630
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British Rail region |
C17999
|
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: British Rail region Context triple: [ER, instanceOf, British Rail region]
-
A.
region of British Railways
chosen
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.
-
B.
former London, Brighton and South Coast Railway network
The former London, Brighton and South Coast Railway network comprises the historic system of main lines, branch lines, and associated infrastructure once operated by the LB&SCR in southern England, primarily serving routes between London, the Sussex coast, and surrounding areas before railway grouping.
-
C.
British Rail Networker unit
A British Rail Networker unit is a family of electric and diesel multiple-unit passenger trains introduced in the late 1980s and 1990s for suburban and commuter services in southeast England.
-
D.
former British Rail sector
A former British Rail sector is an organizational division that once managed specific types of rail services or geographic areas within the state-owned British Rail system before its restructuring and privatization.
-
E.
Scottish railway
A Scottish railway is a rail transport system or line located in Scotland that provides passenger and/or freight services, integrating with the wider UK rail network while serving regional, intercity, and rural connectivity needs.
- 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:01 a.m.