Triple
T8233475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protección Civil de España |
E192348
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civil protection system |
C21507
|
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 protection system Context triple: [Protección Civil de España, instanceOf, civil protection system]
-
A.
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.
-
B.
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.
-
C.
public emergency service system
chosen
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.
-
D.
emergency management framework
An emergency management framework is a structured approach that defines the processes, roles, resources, and coordination mechanisms needed to prepare for, respond to, recover from, and mitigate emergencies and disasters.
-
E.
civil defence equipment
Civil defence equipment comprises tools, devices, and systems designed to protect civilians, support emergency response, and mitigate the impacts of disasters, conflicts, or other large-scale 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:46 p.m.