Triple
T4400518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grigory Zinoviev |
E93603
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bolshevik politician |
C7438
|
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: Bolshevik politician Context triple: [Grigory Zinoviev, instanceOf, Bolshevik politician]
-
A.
Soviet statesman
chosen
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.
Yugoslav politician
A Yugoslav politician is a public official or political leader who operated within the federal structures, republics, or local governments of the former Socialist Federal Republic of Yugoslavia, shaping its domestic and foreign policies during its existence.
-
C.
Belarusian politician
A Belarusian politician is an individual actively involved in the governance, political decision-making, or public administration of Belarus, typically holding or seeking a public office within its political system.
-
D.
anti-Bolshevik leader
An anti-Bolshevik leader is a political or military figure who actively organizes, directs, or symbolizes resistance against Bolshevik ideology, governance, or expansion.
-
E.
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.
- F. None of above.
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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
Created at: March 12, 2026, 11:28 p.m.