Triple
T22388048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN protection of civilians policy framework |
E553444
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | protection of civilians framework |
C15986
|
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: protection of civilians framework Context triple: [UN protection of civilians policy framework, instanceOf, protection of civilians framework]
-
A.
refugee protection framework
A refugee protection framework is a structured set of laws, policies, and procedures designed to ensure the safety, rights, and durable solutions for individuals fleeing persecution, conflict, or serious human rights violations.
-
B.
humanitarian planning framework
chosen
A humanitarian planning framework is a structured approach that guides the assessment, design, implementation, and evaluation of coordinated actions to meet urgent needs and protect the rights of crisis-affected populations.
-
C.
humanitarian protection status
Humanitarian protection status is a legal or administrative designation granted to individuals who cannot safely return to their home country, providing them with temporary or long-term protection, basic rights, and access to essential services.
-
D.
peace and security architecture
A peace and security architecture is an integrated system of institutions, norms, mechanisms, and processes designed to prevent conflict, manage crises, and sustain long-term stability within and among states.
-
E.
civilian victim
A civilian victim is a non-combatant individual who suffers harm, injury, loss, or death as a result of conflict, violence, crime, or disaster.
- 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_69e11e4cf87c8190a1ff474daec326b7 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:45 p.m.