Triple
T21228184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emergency Use Listing by WHO |
E523136
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | emergency use authorization mechanism |
C44403
|
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: emergency use authorization mechanism Context triple: [Emergency Use Listing by WHO, instanceOf, emergency use authorization mechanism]
-
A.
state of emergency authority
State of emergency authority is the legally granted power enabling designated government entities to temporarily suspend or modify normal procedures, rights, and regulations in response to extraordinary crises to protect public safety and order.
-
B.
emergency directive
An emergency directive is an urgent, authoritative instruction issued in response to an immediate threat or crisis, requiring rapid compliance to protect safety, security, or critical operations.
-
C.
emergency legislation
Emergency legislation is a special category of law enacted rapidly, often with expedited procedures and temporary scope, to address urgent or unforeseen crises requiring immediate governmental action.
-
D.
United Nations health emergency mission
A United Nations health emergency mission is a coordinated international operation mandated by the UN to rapidly respond to acute public health crises, providing medical assistance, strengthening local health systems, and supporting disease control and prevention efforts in affected regions.
-
E.
emergency management facility
An emergency management facility is a dedicated center where agencies coordinate, monitor, and direct resources and responses to emergencies and disasters.
- 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:44 p.m.