Triple
T15013040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petro Shelest |
E377886
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ukrainian Soviet statesman |
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: Ukrainian Soviet statesman Context triple: [Petro Shelest, instanceOf, Ukrainian Soviet statesman]
-
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.
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.
-
C.
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.
-
D.
Czechoslovak politician
A Czechoslovak politician is a public figure who held governmental or party office in the former state of Czechoslovakia, influencing its domestic and foreign policies before its dissolution in 1993.
-
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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:55 a.m.