Triple
T25070910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vadim Bakatin |
E627905
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | KGB chairman |
C49405
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: KGB chairman Context triple: [Vadim Bakatin, instanceOf, KGB chairman]
-
A.
Soviet statesman
A Soviet statesman is a high-ranking political leader or government official in the Soviet Union responsible for shaping and implementing state policy, diplomacy, and ideological direction.
-
B.
President of the Russian Soviet Federative Socialist Republic
The President of the Russian Soviet Federative Socialist Republic was the head of state of the RSFSR, serving as its highest executive authority during the final period of the Soviet Union.
-
C.
former prime minister of Russia
A former prime minister of Russia is an individual who previously held the office responsible for leading the Russian government and overseeing the implementation of national policies under the authority of the president.
-
D.
Hungarian communist leader
A Hungarian communist leader is a political figure in Hungary who holds or has held a prominent leadership role within the country’s communist movement or ruling communist party, shaping state policy and ideology according to Marxist-Leninist principles.
-
E.
chairman of the State Duma
The chairman of the State Duma is the presiding officer and highest-ranking official of Russia’s lower house of parliament, responsible for organizing its work, leading plenary sessions, and representing the Duma in relations with other state bodies and external entities.
- F. None of above. chosen
Provenance (1 batch)
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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:10 a.m.