Triple
T34204703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuliy Osipovich Tsederbaum |
E877483
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian Marxist revolutionary |
C32036
|
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: Russian Marxist revolutionary Context triple: [Yuliy Osipovich Tsederbaum, instanceOf, Russian Marxist revolutionary]
-
A.
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.
-
B.
Marxist politician
chosen
A Marxist politician is a political leader or activist who advocates for policies and social structures based on Marxist principles of class struggle, collective ownership, and the abolition of capitalist exploitation.
-
C.
American communist leader
An American communist leader is a political figure in the United States who organizes, advocates, and provides strategic direction for movements and organizations aligned with communist ideology and goals.
-
D.
German revolutionary
A German revolutionary is an individual from Germany who actively seeks to radically transform the existing political, social, or economic order, often through organized resistance, agitation, or direct action.
-
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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:55 a.m.