Triple
T16988460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copernicus Emergency Management Service |
E412130
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | emergency management service |
C5073
|
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 management service Context triple: [Copernicus Emergency Management Service, instanceOf, emergency management service]
-
A.
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.
-
B.
emergency medical service
Emergency medical service is a coordinated system that provides urgent pre-hospital assessment, treatment, and transportation for individuals experiencing acute illness or injury.
-
C.
emergency management agency
chosen
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.
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.
-
E.
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.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:32 a.m.