Triple
T2948646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yakov Dzhugashvili |
E79564
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Yakov |
E79564
|
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: Yakov | Statement: [Yakov Dzhugashvili, givenName, Yakov]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yakov Context triple: [Yakov Dzhugashvili, givenName, Yakov]
-
A.
Yakov
chosen
Yakov was the eldest son of Soviet leader Joseph Stalin, known for his troubled relationship with his father and his death as a prisoner of war during World War II.
-
B.
Semyon
Semyon is a masculine given name of Russian origin, commonly used in Slavic countries.
-
C.
Yefimovich
Yefimovich is the Russian patronymic derived from the male given name Yefim, famously borne by Grigori Rasputin as part of his full name.
-
D.
Yakov Slashchov
Yakov Slashchov was a Russian Imperial and later White Army general best known for leading anti-Bolshevik forces in southern Russia and Crimea during the Russian Civil War.
-
E.
Leonid
Leonid is a masculine given name of Slavic origin, notably borne by Soviet leader Leonid Brezhnev.
- 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_69ad8b1089588190b74d9e2505e45762 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98b6cab88190b4dee7e5ec9347e5 |
completed | March 8, 2026, 3:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b08695bea08190abce552493abda57 |
completed | March 10, 2026, 9:01 p.m. |
Created at: March 8, 2026, 2:57 p.m.