Triple
T30914857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Béla Kun |
E787550
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hungarian Soviet politician |
C9958
|
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: Hungarian Soviet politician Context triple: [Béla Kun, instanceOf, Hungarian Soviet politician]
-
A.
Hungarian communist leader
chosen
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.
-
B.
Hungarian politician
A Hungarian politician is a public figure who participates in the governance and political decision-making processes of Hungary, typically by holding or seeking elected or appointed office at the local, regional, or national level.
-
C.
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.
-
D.
Polish socialist politician
A Polish socialist politician is a public figure from Poland who advocates and implements policies based on socialist principles such as social ownership, economic equality, and expanded welfare within the country’s political system.
-
E.
Communist politician
A communist politician is a public official who advocates for and implements policies based on communist ideology, typically emphasizing collective ownership, class equality, and state or community control of key resources.
- 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_69f224be300c8190a6513ce1ee0a7026 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:51 p.m.