Triple
T21014905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airwave |
E517647
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public safety communications system |
C8046
|
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: public safety communications system Context triple: [Airwave, instanceOf, public safety communications system]
-
A.
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.
-
B.
public safety communications agency
chosen
A public safety communications agency is an organization that manages and coordinates emergency and non-emergency communication services between the public and first responders to ensure timely and effective incident response.
-
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 emergency service system
A public emergency service system is an integrated network of agencies, communication channels, and response resources that coordinates rapid assistance and protection for the public during crises, disasters, and urgent incidents.
-
E.
automotive safety system
An automotive safety system is an integrated set of components and technologies designed to prevent accidents or reduce injury and damage when collisions occur.
- 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_69e0b50262b081909bc488937145eb73 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 1:54 p.m.