Triple
T4200615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1918 influenza pandemic |
E86055
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | global health disaster |
C12805
|
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: global health disaster Context triple: [1918 influenza pandemic, instanceOf, global health disaster]
-
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.
global health report
A global health report is a comprehensive document that compiles, analyzes, and interprets international health data and trends to inform policy decisions, resource allocation, and public health strategies worldwide.
-
C.
global health institution
A global health institution is an organization that coordinates international efforts to prevent disease, promote health, and strengthen health systems across countries through research, policy, funding, and program implementation.
-
D.
infectious disease outbreak
chosen
An infectious disease outbreak is a sudden increase in the occurrence of a specific infectious disease within a particular population, community, or region over a given period of time.
-
E.
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.
- 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_69aed93b89f48190a31f6d57c760e42f |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:49 p.m.