Triple
T6645232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Automatic Train Supervision |
E150683
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rail signaling subsystem |
C3559
|
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 signaling subsystem Context triple: [Automatic Train Supervision, instanceOf, rail signaling subsystem]
-
A.
railway signaling system
chosen
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.
-
B.
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.
-
C.
rail transportation infrastructure
Rail transportation infrastructure encompasses the physical and organizational systems—such as tracks, stations, signaling, power supply, and related facilities—required to support the safe and efficient movement of trains and rail-based services.
-
D.
railway infrastructure element
A railway infrastructure element is any physical component of a rail system—such as tracks, signals, switches, bridges, or platforms—that supports the safe and efficient operation of trains.
-
E.
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.
- 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.