Triple
T1708822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikhail Suslov |
E36931
|
entity |
| Predicate | patronymicName |
P7966
|
FINISHED |
| Object | Andreyevich |
E2779
|
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: Andreyevich | Statement: [Mikhail Suslov, patronymicName, Andreyevich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Andreyevich Context triple: [Mikhail Suslov, patronymicName, Andreyevich]
-
A.
Anatolyevich
Anatolyevich is a Russian patronymic given name indicating that a person is the son of someone named Anatoly.
-
B.
Alexandrovich
Alexandrovich is the Russian patronymic indicating "son of Alexander," famously used in the full name of Tsar Nicholas II of Russia.
-
C.
Andrei
chosen
Andrei is a masculine given name commonly used in Slavic and Eastern European countries, equivalent to the English name Andrew.
-
D.
Vasily Vasiliev
Vasily Vasiliev is a descendant of Soviet leader Joseph Stalin’s family line, being the son of Stalin’s son Vasily Stalin.
-
E.
Konstantin Vershinin
Konstantin Vershinin was a prominent Soviet military leader who served as a senior commander of the Soviet Air Forces during and after World War II.
- 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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa63118618819085700fa84e362d60 |
completed | March 6, 2026, 5:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad8ad849648190b2bb0e2a50cd6c75 |
completed | March 8, 2026, 2:42 p.m. |
Created at: March 4, 2026, 7:30 p.m.