Triple
T18269805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inter-Agency Standing Committee |
E437576
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | humanitarian coordination forum |
C34323
|
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 coordination forum Context triple: [Inter-Agency Standing Committee, instanceOf, humanitarian coordination forum]
-
A.
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.
-
B.
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.
-
C.
humanitarian organizations
chosen
Humanitarian organizations are entities that provide impartial aid, protection, and support to people affected by crises, disasters, and poverty, aiming to alleviate suffering and uphold human dignity.
-
D.
humanitarian initiative
A humanitarian initiative is an organized effort or program designed to alleviate human suffering, protect human rights, and improve the well-being of vulnerable or crisis-affected populations.
-
E.
country-level humanitarian fund
A country-level humanitarian fund is a pooled financing mechanism that channels resources to support timely, coordinated, and flexible humanitarian response within a specific country.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:34 a.m.