Triple
T4131995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNMEER |
E85061
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public health emergency response mission |
C13897
|
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: public health emergency response mission Context triple: [UNMEER, instanceOf, public health emergency response mission]
-
A.
public health emergency
A public health emergency is a situation in which the health of a population is threatened by a significant, often rapidly spreading hazard (such as an infectious disease, environmental exposure, or bioterrorism event) that requires urgent, coordinated public health action and resource mobilization.
-
B.
public health emergency category
A public health emergency category is a classification used to group and prioritize health crises based on their severity, scope, and required response measures to protect population health.
-
C.
crisis-management mandate
A crisis-management mandate is a formal directive that defines the authority, responsibilities, and procedures an organization must follow to prepare for, respond to, and recover from critical incidents or emergencies.
-
D.
rescue mission
A rescue mission is a coordinated operation undertaken to locate, assist, and safely extract individuals or groups from dangerous or life-threatening situations.
-
E.
crisis management activity
chosen
A crisis management activity is a coordinated task or operation undertaken to prepare for, respond to, mitigate, or recover from an unexpected disruptive event that threatens an organization’s objectives or stakeholders.
- 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_69aed935ccd881909dc61f81bcdb7a78 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:42 p.m.