Triple
T7972742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GE Genesis series |
E185366
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | diesel-electric locomotive family |
C23332
|
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: diesel-electric locomotive family Context triple: [GE Genesis series, instanceOf, diesel-electric locomotive 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.
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.
-
C.
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.
-
D.
streamlined locomotive
A streamlined locomotive is a high-speed railway engine designed with smooth, aerodynamic contours to reduce air resistance and improve efficiency and performance.
-
E.
diesel engine family
A diesel engine family is a group of related diesel engines that share a common basic design, architecture, and components but differ in specific configurations such as displacement, power output, and intended applications.
- 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_69ca8297699481909b75a405f01e03af |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:13 p.m.