Triple
T12181305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congresses of the Russian Communist Party (Bolsheviks) |
E290225
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | series of political party congresses |
C5084
|
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: series of political party congresses Context triple: [Congresses of the Russian Communist Party (Bolsheviks), instanceOf, series of political party congresses]
-
A.
party congress
chosen
A party congress is a formal gathering of a political party’s delegates convened to debate policies, elect leadership, and make major organizational decisions.
-
B.
legislative party conference
A legislative party conference is a formal gathering of a political party’s members within a legislative body to coordinate strategy, set policy priorities, and make organizational decisions.
-
C.
series of legislatures
A series of legislatures is a conceptual class representing a sequential collection of legislative bodies or assemblies that convene over successive terms or periods within a political system.
-
D.
series of international conferences
A series of international conferences is a recurring, organized set of global meetings held across different locations and times, bringing together participants from multiple countries to share knowledge, collaborate, and advance a specific field or theme.
-
E.
revolutionary congress
A revolutionary congress is a formal assembly of representatives convened to lead, coordinate, and legitimize a political or social revolution, often drafting new governing frameworks and strategies for transformative change.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:50 p.m.