Triple
T13274603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Fire and Rescue Service |
E316155
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | national emergency service |
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: national emergency service Context triple: [Scottish Fire and Rescue Service, instanceOf, national emergency service]
-
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 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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:26 p.m.