Triple
T8942115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | InterCity East Coast |
E212927
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British Rail sector brand |
C19102
|
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 sector brand Context triple: [InterCity East Coast, instanceOf, British Rail sector brand]
-
A.
former British Rail sector
chosen
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.
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.
-
C.
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.
-
D.
British Railways policy document
A British Railways policy document is an official written directive issued by British Railways that defines rules, procedures, and standards governing its operations, staff conduct, and strategic decisions.
-
E.
high-speed rail service brand
A high-speed rail service brand is a distinct identity and marketing concept that represents a specific provider’s fast, long-distance passenger train services, encompassing its name, visual design, service standards, and customer experience.
- 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_69ca839694c88190b324ffeb43d23b08 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:58 p.m.