Triple
T26870299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilya Yashin |
E676592
|
entity |
| Predicate | hasSpokenOutAbout |
P3281
|
FINISHED |
| Object | assassination of Boris Nemtsov |
—
|
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: assassination of Boris Nemtsov | Statement: [Ilya Yashin, hasSpokenOutAbout, assassination of Boris Nemtsov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpokenOutAbout Context triple: [Ilya Yashin, hasSpokenOutAbout, assassination of Boris Nemtsov]
-
A.
hasSpokenAbout
chosen
Indicates that one entity has verbally expressed, discussed, or mentioned another entity or topic.
-
B.
hasPoliticalActivityIn
Indicates that an entity engages in or is associated with political activities within a specified location or jurisdiction.
-
C.
hasPoliticalDialogue
Indicates that there is an exchange or interaction between entities involving political topics, issues, or negotiations.
-
D.
publicStatements
Indicates that one entity makes official or public verbal or written declarations about another entity or topic.
-
E.
spokenOn
Indicates that an utterance or speech act occurred at or during a specific time or date.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 27, 2026, 5:31 a.m.