Triple
T6645233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Automatic Train Supervision |
E150683
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | train control subsystem |
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: train control subsystem Context triple: [Automatic Train Supervision, instanceOf, train control subsystem]
-
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.
railway signaling system
A railway signaling system is an integrated set of trackside and onboard equipment, rules, and communication protocols that control train movements to ensure safe separation, efficient routing, and protection against collisions.
-
C.
rail transit
Rail transit is a public transportation system that moves passengers or freight along fixed steel tracks using trains, subways, trams, or light rail vehicles, typically in urban or intercity corridors.
-
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.
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.
- 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_69c687f1a3048190828b7342f7125d5c |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2 p.m.