Triple
T26208912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Essex Thameside franchise |
E655430
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UK rail franchise |
C20589
|
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: UK rail franchise Context triple: [Essex Thameside franchise, instanceOf, UK rail franchise]
-
A.
former British rail franchise operator
chosen
A former British rail franchise operator is a company that previously held a government-awarded contract to run passenger train services on specific routes or regions within the UK rail network.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
Created at: April 26, 2026, 8:51 p.m.