Triple
T25314903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 317 |
E634708
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British Rail EMU |
C50014
|
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 EMU Context triple: [British Rail Class 317, instanceOf, British Rail EMU]
-
A.
British Rail second-generation DMU
A British Rail second-generation DMU is a diesel multiple unit train introduced from the 1980s onward, featuring improved performance, comfort, and safety over first-generation units and designed for regional and suburban passenger services across the UK rail network.
-
B.
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.
-
C.
British Rail Mark 3 variant
A British Rail Mark 3 variant is a specific version of the Mark 3 passenger rail coach, modified or configured for particular operational roles, comfort standards, or railway operators.
-
D.
British Rail Mark 2 coach variant
A British Rail Mark 2 coach variant is a specific design iteration within the Mark 2 family of passenger railway carriages, distinguished by particular structural, interior, and technical features tailored to different service requirements and eras.
-
E.
British Rail Mark 3 coach sub-series
The British Rail Mark 3 coach sub-series comprises the various specialized variants of the Mark 3 passenger coach design, each adapted for different operators, services, and technical requirements within the UK rail network.
- F. None of above. chosen
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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:27 p.m.