Triple
T10108826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Committee of Members of the Constituent Assembly |
E218189
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | anti-Bolshevik political organization |
C27416
|
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: anti-Bolshevik political organization Context triple: [Committee of Members of the Constituent Assembly, instanceOf, anti-Bolshevik political organization]
-
A.
anti-Bolshevik government
An anti-Bolshevik government is a political authority formed in opposition to Bolshevik rule, typically seeking to resist, overturn, or prevent the establishment of a Bolshevik-led socialist or communist regime.
-
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.
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.
-
D.
Ukrainian nationalist organization
A Ukrainian nationalist organization is a group dedicated to promoting and defending the political, cultural, and historical interests, identity, and sovereignty of the Ukrainian nation.
-
E.
Afghan political organization
An Afghan political organization is a structured group operating within Afghanistan’s political sphere that seeks to influence governance, policy, and public opinion through formal or informal means.
- F. None of above. chosen
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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 9:03 p.m.