Triple
T24284002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 911 dispatch system of Washington, D.C. |
E605620
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | emergency 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: emergency communications system Context triple: [911 dispatch system of Washington, D.C., instanceOf, emergency communications system]
-
A.
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.
-
B.
emergency alerting standard
An emergency alerting standard is a formal specification that defines how urgent public safety messages are created, formatted, transmitted, and delivered across communication systems to warn and inform people during crises.
-
C.
civil emergency service
A civil emergency service is a public organization responsible for preparing for, responding to, and managing non-military crises and disasters to protect people, property, and the environment.
-
D.
emergency directive
An emergency directive is an urgent, authoritative instruction issued in response to an immediate threat or crisis, requiring rapid compliance to protect safety, security, or critical operations.
-
E.
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.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:08 a.m.