Triple
T26927367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SP 4279 |
E678115
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | EMD SD9 |
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: EMD SD9 Context triple: [SP 4279, instanceOf, EMD SD9]
-
A.
EMD 710 series engine
The EMD 710 series engine is a two-stroke, turbocharged diesel locomotive and marine prime mover known for its modular design, high power-to-weight ratio, and improved fuel efficiency over earlier EMD engine families.
-
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.
diesel-electric locomotive family
chosen
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.
-
D.
Southern Pacific Railroad steam locomotive class
A Southern Pacific Railroad steam locomotive class is a group of steam engines built or rostered by the Southern Pacific Railroad that share common design, performance, and operational characteristics for specific types of rail service.
-
E.
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.
- 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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 6:10 a.m.