Triple
T23324162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hitachi A-Train |
E591241
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | electric multiple unit family |
C19529
|
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: electric multiple unit family Context triple: [Hitachi A-Train, instanceOf, electric multiple unit 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.
diesel-electric locomotive family
A diesel-electric locomotive family is a group of closely related locomotive models that share a common diesel engine and electric transmission design, with variations in power, configuration, and features tailored to different rail service needs.
-
C.
Electrostar family
chosen
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.
-
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.
passenger railcar fleet
A passenger railcar fleet is a managed collection of rail vehicles designed and maintained to transport people safely and efficiently across a 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_69e25d1effe4819096907f95f610dbff |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:08 p.m.