Triple
T36771898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hampshire County Regional Emergency Communication Center |
E908500
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | emergency communication center |
C62239
|
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 communication center Context triple: [Hampshire County Regional Emergency Communication Center, instanceOf, emergency communication center]
-
A.
emergency medical dispatch center
chosen
An emergency medical dispatch center is a coordinated communication hub that receives urgent calls, assesses medical needs, and dispatches appropriate emergency medical services and resources.
-
B.
emergency management facility
An emergency management facility is a dedicated center where agencies coordinate, monitor, and direct resources and responses to emergencies and disasters.
-
C.
emergency management agency
An emergency management agency is an organization responsible for preparing for, coordinating, and responding to natural or human-made disasters to protect people, property, and the environment.
-
D.
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.
-
E.
emergency services district
An emergency services district is a defined geographic area governed by a special-purpose local authority that organizes, funds, and oversees emergency response services such as fire protection, EMS, and rescue operations for the communities within its boundaries.
- 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.