Triple
T31100280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosamund |
E792653
|
entity |
| Predicate | allegedAct |
P52031
|
FINISHED |
| Object | poisoning of Helmichis |
—
|
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 of Helmichis | Statement: [Rosamund, allegedAct, poisoning of Helmichis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedAct Context triple: [Rosamund, allegedAct, poisoning of Helmichis]
-
A.
allegedAction
chosen
Indicates that an action is claimed or asserted to have occurred, typically without being proven or confirmed.
-
B.
allegedClause
Indicates that a clause or statement is claimed or asserted to be true, typically without confirmed proof or legal determination.
-
C.
allegedActor
Indicates that the subject is claimed or accused to be the actor responsible for a particular action or event, without confirming that the claim is true.
-
D.
allegedUse
Indicates that something is claimed or suspected to have been used, without confirming that the use actually occurred.
-
E.
accusedOf
Indicates that one entity has formally alleged or claimed that another entity committed a specific wrongdoing or offense.
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 29, 2026, 9:03 p.m.