Triple
T30181777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail sectorisation era |
E767220
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | phase of British Rail history |
C54422
|
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: phase of British Rail history Context triple: [British Rail sectorisation era, instanceOf, phase of British Rail history]
-
A.
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.
-
B.
division of the British Transport Commission
A division of the British Transport Commission is an organizational unit within the former nationalized body responsible for managing and coordinating specific sectors or functions of Britain’s transport system, such as railways, road transport, docks, or inland waterways.
-
C.
railway history era
chosen
A railway history era is a distinct period characterized by specific technological, operational, and social developments in the evolution of rail transport.
-
D.
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.
-
E.
British Rail EMU
A British Rail EMU is an electric multiple unit train operated on the British railway network, consisting of self-propelled carriages powered by electricity from overhead lines or third-rail systems for passenger service.
- 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_69f2247cc3d88190811dec3face94bf5 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:26 p.m.