Triple
T4420722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humanitarian Response Plan |
E95090
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | humanitarian planning 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: humanitarian planning framework Context triple: [Humanitarian Response Plan, instanceOf, humanitarian planning framework]
-
A.
United Nations strategic planning framework
The United Nations strategic planning framework is a structured, organization-wide approach that aligns UN mandates, goals, resources, and performance measures to guide coherent, long-term action across agencies and member states.
-
B.
WHO framework
The WHO framework is a structured, evidence-based model developed by the World Health Organization to guide global health policy, planning, and interventions across health systems, disease control, and population well-being.
-
C.
disaster management initiative
A disaster management initiative is a coordinated program or effort designed to prevent, prepare for, respond to, and recover from natural or human-made disasters to protect lives, property, and the environment.
-
D.
humanitarian emblem
A humanitarian emblem is a universally recognized protective symbol used in armed conflicts and emergencies to identify and safeguard medical services, relief personnel, and facilities under international humanitarian law.
-
E.
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.
- 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_69b3453a36908190b95a79a297ca083c |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:30 p.m.