Triple
T30953191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ETCS Level 0 |
E788601
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ETCS operating level |
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: ETCS operating level Context triple: [ETCS Level 0, instanceOf, ETCS operating level]
-
A.
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.
-
B.
operational railway route grouping
An operational railway route grouping is a structured collection of railway routes combined for coordinated planning, management, and control of train operations across a defined network segment.
-
C.
InterCityExpress variant
An InterCityExpress variant is a specific model or configuration of high-speed ICE train designed for particular routes, capacities, or service requirements within an intercity rail network.
-
D.
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.
-
E.
transport infrastructure operator
A transport infrastructure operator is an entity responsible for managing, maintaining, and regulating transportation networks and facilities such as roads, railways, ports, or airports to ensure safe and efficient movement of people and goods.
- 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:53 p.m.