Triple
T25220256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warrandyte Fire Brigade |
E631942
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | emergency response organisation |
C48585
|
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 response organisation Context triple: [Warrandyte Fire Brigade, instanceOf, emergency response organisation]
-
A.
crisis response organization
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.
-
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 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.
-
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 provider
chosen
An emergency services provider is an organization or individual that delivers urgent, often life-saving assistance in response to crises, accidents, or disasters, such as medical emergencies, fires, or public safety threats.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
Created at: April 21, 2026, 1:03 p.m.