Triple
T23499663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Automatic Train Operation |
E571804
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway 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: railway control system Context triple: [Automatic Train Operation, instanceOf, railway 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.
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.
railway communication system
A railway communication system is an integrated network of technologies and protocols that enable real-time exchange of information between trains, trackside equipment, and control centers to ensure safe, efficient, and coordinated railway operations.
-
D.
public railway
A public railway is a government- or publicly-owned rail transport system that provides scheduled passenger and/or freight services accessible to the general population, typically operating on standardized tracks and infrastructure.
-
E.
railway classification system
A railway classification system is a structured framework used to categorize railways, trains, or rail services based on characteristics such as function, capacity, speed, infrastructure, or ownership.
- 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 6:06 p.m.