Triple
T25609900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Amesbury poisoning |
E642017
|
entity |
| Predicate | objectInvolved |
P126429
|
FINISHED |
| Object | discarded container found by victim |
—
|
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: discarded container found by victim | Statement: [2018 Amesbury poisoning, objectInvolved, discarded container found by victim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectInvolved Context triple: [2018 Amesbury poisoning, objectInvolved, discarded container found by victim]
-
A.
materialInvolved
Indicates that a particular material participates in, is used by, or is otherwise involved in the referenced process, event, or relationship.
-
B.
objectUsed
chosen
Indicates that one entity is used as a tool, instrument, or resource in performing an action involving another entity.
-
C.
utilityInvolved
Indicates that a utility service or provider is involved in, associated with, or plays a role in the referenced situation or relationship.
-
D.
involvedAction
Indicates that an entity participates in, performs, or is otherwise engaged in a specified action or activity.
-
E.
objet
Indicates that one entity is the object (recipient or target) of an action or relation performed by another entity.
- 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_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_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 4:40 p.m.