Triple
T23966064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Dying epidemic of 1616–1619 |
E604085
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | health disaster |
C223
|
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: health disaster Context triple: [Great Dying epidemic of 1616–1619, instanceOf, health disaster]
-
A.
disaster
chosen
A disaster is a sudden, disruptive event—natural or human-made—that causes significant harm to people, property, or the environment and overwhelms normal coping capacities.
-
B.
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.
-
C.
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.
-
D.
health incident pattern
A health incident pattern is a recurring or recognizable sequence of health-related events, symptoms, or conditions that reveals underlying trends, risks, or causal relationships in individual or population health.
-
E.
disaster management initiative
A disaster management initiative is a coordinated program or effort designed to prevent, prepare for, respond to, and recover from natural or human-made disasters to protect lives, property, and the environment.
- 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 17, 2026, 9:24 p.m.