Triple
T23777692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walter Devereux, 1st Earl of Essex |
E587719
|
entity |
| Predicate | rumor |
P26076
|
FINISHED |
| Object | poisoning at Dublin |
—
|
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: poisoning at Dublin | Statement: [Walter Devereux, 1st Earl of Essex, rumor, poisoning at Dublin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rumor Context triple: [Walter Devereux, 1st Earl of Essex, rumor, poisoning at Dublin]
-
A.
rumorContent
Indicates that the associated information specifies the subject matter or details contained within a particular rumor.
-
B.
rumoredTarget
chosen
Indicates that an entity is believed or speculated, based on rumor or unconfirmed information, to be the intended target of another entity or action.
-
C.
rumoredTrait
Indicates that a particular trait is attributed to an entity based on rumor or unverified reports rather than confirmed fact.
-
D.
heard
Indicates that one entity perceived a sound produced by another entity or source through hearing.
-
E.
conspiracy
Indicates a secret agreement or collaboration between multiple entities to plan or carry out an unlawful, deceptive, or harmful act.
- 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_69e2490d245881909028226a1393d624 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c46d55588190ad9c7e3c729b6b17 |
completed | April 29, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:16 p.m.