Triple
T33003393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Resilience Forum |
E844431
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civil contingencies coordination body |
C41267
|
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: civil contingencies coordination body Context triple: [Local Resilience Forum, instanceOf, civil contingencies coordination body]
-
A.
civil-military coordination structure
A civil-military coordination structure is an organized framework that defines roles, processes, and communication channels between civilian authorities and military forces to plan, manage, and execute joint operations effectively and lawfully.
-
B.
humanitarian assistance coordination body
chosen
A humanitarian assistance coordination body is an organized entity that brings together multiple stakeholders to plan, align, and oversee the delivery of humanitarian aid to affected populations efficiently and effectively.
-
C.
intelligence coordination body
An intelligence coordination body is an organization responsible for integrating, harmonizing, and directing the activities, information sharing, and strategic priorities of multiple intelligence agencies or units to support national or organizational security objectives.
-
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.
civil affairs unit
A civil affairs unit is a military organization responsible for managing relationships and coordination between armed forces and civilian populations, authorities, and institutions in areas of operation.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:23 a.m.