Triple
T27312864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daria Navalnaya |
E689253
|
entity |
| Predicate | publiclyCommentedOn |
P149368
|
FINISHED |
| Object | poisoning of Alexei Navalny |
—
|
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 Alexei Navalny | Statement: [Daria Navalnaya, publiclyCommentedOn, poisoning of Alexei Navalny]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publiclyCommentedOn Context triple: [Daria Navalnaya, publiclyCommentedOn, poisoning of Alexei Navalny]
-
A.
commentedOnBy
Indicates that an entity has received a comment authored or posted by another entity.
-
B.
hasPublicComment
chosen
Indicates that an entity is associated with one or more comments that are visible to the general public.
-
C.
commentatedFor
Indicates that one entity provided live or recorded commentary or analysis for an event, performance, or broadcast on behalf of another entity (such as an organization, channel, or client).
-
D.
difficultyCommentedOnBy
Indicates that a particular difficulty or challenge has been commented on or discussed by a specific entity.
-
E.
publiclyDisplayed
Indicates that something is shown or made visible in a public context or setting, accessible to people at large.
- 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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 27, 2026, 11:28 a.m.