Triple
T28407887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emergency Medical Services Division |
E719584
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public safety agency unit |
C9931
|
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 agency unit Context triple: [Emergency Medical Services Division, instanceOf, public safety agency unit]
-
A.
public safety agency
chosen
A public safety agency is an organization responsible for protecting the public from threats and hazards by preventing, responding to, and managing emergencies, crimes, and disasters within a community or jurisdiction.
-
B.
law enforcement unit
A law enforcement unit is an organized group within a policing or security agency tasked with enforcing laws, maintaining public order, and conducting specialized operations or investigations.
-
C.
public safety communications agency
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.
-
D.
security and intelligence unit
A security and intelligence unit is an organized group responsible for gathering, analyzing, and acting on information to prevent threats and protect people, assets, and critical operations.
-
E.
transportation safety agency
A transportation safety agency is an organization responsible for regulating, monitoring, and enforcing safety standards across transportation systems to prevent accidents and protect the public.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:24 a.m.