Triple
T28480052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ley 2/1985 de Protección Civil |
E720667
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | norma básica de protección civil |
C54110
|
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: norma básica de protección civil Context triple: [Ley 2/1985 de Protección Civil, instanceOf, norma básica de protección civil]
-
A.
BCP
BCP is a Business Continuity Plan that outlines procedures and resources to ensure critical business functions continue or are quickly restored during and after a disruption.
-
B.
U.S. national preparedness framework
The U.S. national preparedness framework is a coordinated, all-hazards structure that defines roles, responsibilities, and core capabilities across government and society to prevent, protect against, mitigate, respond to, and recover from disasters and emergencies.
-
C.
municipal protection category
A municipal protection category is a classification used by local governments to designate and regulate areas, structures, or resources that require specific protective measures due to their environmental, cultural, historical, or public safety significance.
-
D.
protective zone
A protective zone is a designated area or boundary established to shield people, assets, or environments from potential harm, hazards, or unauthorized influence.
-
E.
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.
- F. None of above. chosen
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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 2:54 a.m.