Triple
T34865262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Lakes refugee crises |
E1004991
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | humanitarian emergency |
C61841
|
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 emergency Context triple: [Great Lakes refugee crises, instanceOf, humanitarian emergency]
-
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 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.
-
C.
humanitarian funding appeal
A humanitarian funding appeal is a formal request issued by organizations or authorities to mobilize financial resources for urgent relief and recovery efforts in response to crises or disasters.
-
D.
humanitarian organizations
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.
-
E.
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.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.