Triple
T9555019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TVM cab signalling |
E230519
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | in-cab signalling system |
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: in-cab signalling system Context triple: [TVM cab signalling, instanceOf, in-cab signalling system]
-
A.
streetcar system
A streetcar system is an urban public transit network that operates rail vehicles on fixed tracks, typically embedded in city streets, to transport passengers along defined routes.
-
B.
public transit fare payment system
A public transit fare payment system manages the calculation, collection, validation, and tracking of passenger payments across various transit services and media (e.g., cards, mobile apps, tickets) to authorize and record travel.
-
C.
cable car system
A cable car system is a transportation network in which vehicles are pulled by continuously moving cables, typically used to move people or goods along steep or inaccessible routes such as mountainsides or urban hills.
-
D.
public safety system
A public safety system is an integrated framework of technologies, policies, and coordinated services designed to prevent, detect, respond to, and recover from threats or emergencies affecting the well-being of a community.
-
E.
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.
- 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_69ca847d3be8819099c9dad2a7e786f1 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:03 p.m.