Triple
T3224109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maxim Peshkov |
E67581
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Peshkov |
E336064
|
NE 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: Peshkov | Statement: [Maxim Peshkov, familyName, Peshkov]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Peshkov Context triple: [Maxim Peshkov, familyName, Peshkov]
-
A.
Peshkov
chosen
Peshkov is a Russian surname most famously borne by Alexei Maximovich Peshkov, better known by his pen name Maxim Gorky, a prominent writer and political activist.
-
B.
Lukyanov
Lukyanov is a Russian surname borne by various notable figures in politics, science, and the arts.
-
C.
Chernyakhovsky
Chernyakhovsky is a Slavic surname most notably associated with Soviet General Ivan Chernyakhovsky, a prominent commander during World War II.
-
D.
Krasnov
Krasnov is a Russian surname borne by various notable figures in military, political, and cultural history.
-
E.
Pozdnyshev
Pozdnyshev is the tormented, jealous husband and central narrator of Leo Tolstoy’s novella "The Kreutzer Sonata," whose confession of murdering his wife drives the story’s exploration of marriage, sexuality, and morality.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ad858b8adc8190ad989712c87a476b |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adae1ae8f08190880d0f0e8539cdbc |
completed | March 8, 2026, 5:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b27726f76c819092a199ae07a7e688 |
completed | March 12, 2026, 8:19 a.m. |
Created at: March 8, 2026, 3:08 p.m.