Triple
T12539992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suffolk Fire and Rescue Service |
E299810
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | emergency services organisation |
C15106
|
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 services organisation Context triple: [Suffolk Fire and Rescue Service, instanceOf, emergency services organisation]
-
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 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
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 management training organization
An emergency management training organization designs and delivers specialized education, simulations, and certification programs to prepare individuals and agencies to effectively prevent, respond to, and recover from emergencies and disasters.
-
E.
crisis response organization
chosen
A crisis response organization is an entity that rapidly coordinates resources, personnel, and communication to assess, manage, and mitigate emergencies or disasters affecting people, infrastructure, or the environment.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:57 p.m.