Triple
T20772229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Mark 3 coaching stock |
E511264
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British Rail carriage design |
C19300
|
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 carriage design Context triple: [British Rail Mark 3 coaching stock, instanceOf, British Rail carriage design]
-
A.
railway vehicle design
chosen
Railway vehicle design is the engineering discipline focused on conceptualizing, developing, and optimizing rail vehicles for performance, safety, comfort, and compatibility with railway infrastructure and operations.
-
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.
rail vehicle
A rail vehicle is a wheeled conveyance designed to operate on railway tracks for transporting passengers, freight, or performing specialized rail-related tasks.
-
D.
historical railway asset
A historical railway asset is any preserved or documented physical or digital artifact—such as tracks, rolling stock, stations, equipment, or records—associated with past railway operations and valued for its cultural, technological, or historical significance.
-
E.
rolling stock
Rolling stock refers to all the vehicles that move on a railway, including locomotives, passenger coaches, freight wagons, and maintenance units.
- 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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:37 p.m.