Triple
T7025168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Antonov |
E162926
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian Socialist Revolutionary |
C8726
|
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 Socialist Revolutionary Context triple: [Alexander Antonov, instanceOf, Russian Socialist 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.
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.
-
C.
Communist
A Communist is an individual who advocates for a classless, stateless society in which the means of production are collectively owned and resources are distributed according to need.
-
D.
Trotskyist international organization
A Trotskyist international organization is a transnational political association that coordinates parties and groups committed to Leon Trotsky’s theories of permanent revolution, proletarian internationalism, and opposition to Stalinism.
-
E.
Nationalist revolutionary
chosen
A nationalist revolutionary is an individual who seeks to overthrow existing political structures and mobilize mass support to establish an independent or radically transformed nation-state based on a shared national identity.
- 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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:35 p.m.