Triple
T154222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Health Emergency of International Concern |
E3142
|
entity |
| Predicate | criteriaIncludes |
P1393
|
FINISHED |
| Object | serious public health impact |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: serious public health impact | Statement: [Public Health Emergency of International Concern, criteriaIncludes, serious public health impact]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: criteriaIncludes Context triple: [Public Health Emergency of International Concern, criteriaIncludes, serious public health impact]
-
A.
selectionCriteria
Indicates the conditions or rules used to choose certain entities from a larger set.
-
B.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
C.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
D.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
E.
meetsEvery
Indicates that one entity encounters or comes into contact with every member of a specified set of entities.
- F. None of above.
Provenance (3 batches)
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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a258e0b11c8190b7b5cf3c354c47ce |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a2565c727c8190bca9ba6ca52f216a |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.