Triple
T13455520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westinghouse H2C |
E311221
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | electric multiple-unit coupler system |
C18983
|
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 coupler system Context triple: [Westinghouse H2C, instanceOf, electric multiple-unit coupler system]
-
A.
railway coupling system
chosen
A railway coupling system is a mechanical assembly that connects railway vehicles together, transmitting forces for traction and braking while maintaining alignment and safe separation between cars.
-
B.
automatic coupler
An automatic coupler is a self-acting mechanical device used to connect and disconnect railway vehicles (or similar rolling stock) without manual intervention, ensuring secure, rapid, and standardized coupling.
-
C.
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.
-
D.
third rail electrification system
A third rail electrification system is a method of providing electric power to trains via an additional rail mounted alongside or between the running rails, from which current is collected by contact shoes on the train.
-
E.
electrified railway
An electrified railway is a rail transport system in which trains receive power from external electrical sources, such as overhead lines or third rails, instead of relying on onboard fuel.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:41 p.m.