Triple
T25609889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Amesbury poisoning |
E642017
|
entity |
| Predicate | riskToPublic |
P158910
|
FINISHED |
| Object | initially assessed as low |
—
|
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: initially assessed as low | Statement: [2018 Amesbury poisoning, riskToPublic, initially assessed as low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskToPublic Context triple: [2018 Amesbury poisoning, riskToPublic, initially assessed as low]
-
A.
riskToUser
Indicates that something poses a potential danger, harm, or adverse impact to the user.
-
B.
riskToSpeaker
Indicates that the action, event, or situation poses a potential danger, harm, or adverse consequence to the speaker.
-
C.
riskListedBy
Indicates that a risk has been documented, identified, or cataloged by a particular agent or source.
-
D.
riskType
Indicates the category or nature of risk associated with an entity, event, or relationship.
-
E.
riskElement
Indicates that one entity is a risk-related component, factor, or contributor associated with another entity within a risk context.
- F. None of above. chosen
Provenance (4 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9e1f1408190bab690f67f7d3a31 |
completed | May 2, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 4:40 p.m.