Triple
T38344718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westinghouse XA traction control (as built) |
E1041507
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rail vehicle propulsion control system |
C3558
|
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: rail vehicle propulsion control system Context triple: [Westinghouse XA traction control (as built), instanceOf, rail vehicle propulsion control system]
-
A.
train control system
chosen
A train control system is a coordinated set of hardware and software components that monitor, regulate, and automate train movements to ensure safe, efficient, and reliable railway operations.
-
B.
rail vehicle
A rail vehicle is a wheeled conveyance designed to operate on railway tracks for transporting passengers, freight, or performing specialized rail-related tasks.
-
C.
railway vehicle design
Railway vehicle design is the engineering discipline focused on conceptualizing, developing, and optimizing rail vehicles for performance, safety, comfort, and compatibility with railway infrastructure and operations.
-
D.
electrified railway operation
Electrified railway operation is the management and control of train services powered by electrical energy supplied through overhead lines or third rails, encompassing infrastructure, rolling stock, power systems, and operational procedures to ensure safe, efficient, and reliable transport.
-
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_69f76e2ad95481908c920c0e5c1c3e26 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:30 p.m.