Triple
T8581719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuri Shchekochikhin |
E203196
|
entity |
| Predicate | allegedVictimOf |
P82962
|
FINISHED |
| Object | politically motivated poisoning |
—
|
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: politically motivated poisoning | Statement: [Yuri Shchekochikhin, allegedVictimOf, politically motivated poisoning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedVictimOf Context triple: [Yuri Shchekochikhin, allegedVictimOf, politically motivated poisoning]
-
A.
isVictimOf
Indicates that one entity suffers harm, loss, or wrongdoing as a result of another entity’s actions or events.
-
B.
portraysAsVictim
Indicates that one entity represents or depicts another entity as a victim in a given context or narrative.
-
C.
secondAllegedVictim
Indicates that an entity is identified as the second person alleged to have been victimized in relation to another entity or incident.
-
D.
honorsVictimOf
Indicates that one entity pays tribute or respect to another entity who has suffered harm, loss, or injustice.
-
E.
coVictim
Indicates that two or more entities are victims in the same harmful event or incident.
- 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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbeb1bbbd8819082670286a711826d |
completed | March 31, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69cbd11b13108190b07f8f161425a585 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe12dd0b88190a38ec4d15dcc870b |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 6:22 p.m.