Triple
T12360640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King County Fire Protection District 14 |
E294725
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | emergency services jurisdiction |
C19840
|
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 jurisdiction Context triple: [King County Fire Protection District 14, instanceOf, emergency services jurisdiction]
-
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.
legal jurisdiction
chosen
A legal jurisdiction is a defined geographic area or subject-matter domain within which a particular court or governmental authority has the power to create, interpret, and enforce laws.
-
E.
civil affairs capacity
Civil affairs capacity is the ability of an organization or force to plan, coordinate, and execute activities that manage relationships and support between civilian populations, local institutions, and military or governmental operations in complex environments.
- 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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:54 p.m.