Triple
T10653914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 46664 campaign |
E251040
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | humanitarian initiative |
C28805
|
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 initiative Context triple: [46664 campaign, instanceOf, humanitarian initiative]
-
A.
humanitarian relief operation
A humanitarian relief operation is a coordinated effort to rapidly provide essential aid, services, and protection to populations affected by crises such as natural disasters, conflicts, or epidemics, aiming to save lives, alleviate suffering, and support basic human dignity.
-
B.
humanitarian health organization
A humanitarian health organization is an entity that delivers medical care, public health services, and health-related support to vulnerable or crisis-affected populations, prioritizing equity, neutrality, and rapid response to human suffering.
-
C.
human rights initiative
A human rights initiative is an organized effort or program aimed at promoting, protecting, and advancing fundamental human rights and freedoms for individuals or communities.
-
D.
humanitarian information service
A humanitarian information service is a system that collects, manages, and disseminates critical, reliable information to support decision-making and coordination in humanitarian crises.
-
E.
humanitarian planning framework
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.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:06 p.m.