Triple
T16496057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Region |
E400687
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British Railways 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 Railways region Context triple: [Scottish Region, instanceOf, British Railways 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 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.
-
C.
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.
-
D.
former British rail franchise operator
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.
-
E.
group of railway companies
A group of railway companies is an organized association of multiple rail transport operators that collaborate or are collectively managed to provide coordinated rail services, share resources, or pursue common commercial or regulatory interests.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:14 a.m.