Triple
T14264967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siemens Desiro |
E353621
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multiple unit train family |
C29558
|
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: multiple unit train family Context triple: [Siemens Desiro, instanceOf, multiple unit train family]
-
A.
diesel-electric multiple unit family
A diesel-electric multiple unit family is a group of closely related self-propelled rail vehicles that use onboard diesel engines to generate electricity for traction motors, sharing common design, components, and performance characteristics.
-
B.
passenger railcar family
A passenger railcar family is a group of related rail vehicles sharing a common design platform, structural features, and systems, adapted into multiple variants to serve different passenger transport roles and service requirements.
-
C.
multiple unit
chosen
A multiple unit is a self-propelled trainset composed of permanently or semi-permanently coupled cars, each equipped with its own traction and control systems, allowing the entire consist to be operated from a single cab.
-
D.
bi-mode multiple unit train
A bi-mode multiple unit train is a self-propelled trainset capable of operating using both external electric power (from overhead lines or third rail) and onboard diesel or battery power, allowing seamless running across electrified and non-electrified routes.
-
E.
Electrostar family
The Electrostar family is a series of modern electric multiple-unit passenger trains designed for suburban and regional services, known for their modular construction and widespread use in the UK rail network.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:09 a.m.