Triple
T7080773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vasily Sokolovsky |
E164947
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object |
Sokolovsky
Sokolovsky is a Russian surname most notably associated with Soviet military commander Vasily Sokolovsky.
|
E643755
|
NE FINISHED |
How this triple was built (4 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: Sokolovsky | Statement: [Vasily Sokolovsky, familyName, Sokolovsky]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sokolovsky Context triple: [Vasily Sokolovsky, familyName, Sokolovsky]
-
A.
Firsov
Firsov is a Russian surname most notably associated with Anatoli Firsov, a legendary Soviet ice hockey forward.
-
B.
Vasilevsky
Vasilevsky is a Russian surname most prominently associated with Aleksandr Vasilevsky, a leading Soviet military commander and Marshal of the Soviet Union during World War II.
-
C.
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.
-
D.
Lukyanov
Lukyanov is a Russian surname borne by various notable figures in politics, science, and the arts.
-
E.
Alekseyev
Alekseyev is a Russian surname borne by various notable figures in Russian history, military, and culture.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Sokolovsky Triple: [Vasily Sokolovsky, familyName, Sokolovsky]
Generated description
Sokolovsky is a Russian surname most notably associated with Soviet military commander Vasily Sokolovsky.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Sokolovsky Target entity description: Sokolovsky is a Russian surname most notably associated with Soviet military commander Vasily Sokolovsky.
-
A.
Firsov
Firsov is a Russian surname most notably associated with Anatoli Firsov, a legendary Soviet ice hockey forward.
-
B.
Vasilevsky
Vasilevsky is a Russian surname most prominently associated with Aleksandr Vasilevsky, a leading Soviet military commander and Marshal of the Soviet Union during World War II.
-
C.
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.
-
D.
Lukyanov
Lukyanov is a Russian surname borne by various notable figures in politics, science, and the arts.
-
E.
Alekseyev
Alekseyev is a Russian surname borne by various notable figures in Russian history, military, and culture.
- F. None of above. chosen
Provenance (5 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_69c6887cbc6c8190bdfac42d940f4d8a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4f1f5748190b214856bcfc70d81 |
completed | March 27, 2026, 8:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7a31c26808190870e6bcdef45d1d7 |
completed | March 28, 2026, 9:45 a.m. |
| NEDg | Description generation | batch_69c7a48bd2048190869c4e15c9c016b8 |
completed | March 28, 2026, 9:51 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c7a5f558788190805a0c87b2390a8d |
completed | March 28, 2026, 9:57 a.m. |
Created at: March 27, 2026, 2:40 p.m.