Triple
T20316203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ETH (Electric Train Heating) |
E510385
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | train onboard services power system |
C43642
|
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: train onboard services power system Context triple: [ETH (Electric Train Heating), instanceOf, train onboard services power system]
-
A.
train control system
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.
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.
-
C.
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.
-
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.
power system
A power system is an interconnected network of generation, transmission, distribution, and control components designed to produce and deliver electrical energy reliably and efficiently to end users.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 11:19 a.m.