Triple
T25609859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Amesbury poisoning |
E642017
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public health incident |
C49045
|
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 incident Context triple: [2018 Amesbury poisoning, instanceOf, public health incident]
-
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.
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.
-
C.
public health issue
chosen
A public health issue is a condition or factor that negatively affects the health of a population and requires collective, often policy-driven, interventions to prevent, control, or mitigate its impact.
-
D.
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.
-
E.
infectious disease outbreak
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.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 4:40 p.m.