Triple
T20316106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Mark 1 coaching stock |
E510383
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British Rail rolling stock class |
C8948
|
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 rolling stock class Context triple: [British Rail Mark 1 coaching stock, instanceOf, British Rail rolling stock class]
-
A.
railway locomotive class
A railway locomotive class is a categorization of locomotives that share common design, performance, and functional characteristics, typically used for identification, operation, and maintenance purposes.
-
B.
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.
-
C.
rolling stock
chosen
Rolling stock refers to all the vehicles that move on a railway, including locomotives, passenger coaches, freight wagons, and maintenance units.
-
D.
electric locomotive class
An electric locomotive class is a category of railway locomotives designed and grouped by shared technical and performance characteristics, all powered by electricity from external sources such as overhead lines or third rails.
-
E.
railroad rolling stock identifier
A railroad rolling stock identifier is a unique code or marking assigned to each rail vehicle to distinguish it from others for tracking, operations, and maintenance purposes.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 11:19 a.m.