Triple
T7394321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Станіслав Вікентійович Косіор |
E170582
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | радянський державний діяч |
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: радянський державний діяч Context triple: [Станіслав Вікентійович Косіор, instanceOf, радянський державний діяч]
-
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.
Soviet revolutionary
A Soviet revolutionary is an individual who actively participated in or supported the political, social, and often armed struggle to overthrow the existing order and establish or advance the socialist state in the former Soviet Union.
-
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.
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.
- 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_69c68a5f04188190ac266569c9280347 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:09 p.m.