Triple
T10932552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Revolutionary Committee of the Petrograd Soviet |
E258244
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | revolutionary committee |
C28580
|
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: revolutionary committee Context triple: [Military Revolutionary Committee of the Petrograd Soviet, instanceOf, revolutionary committee]
-
A.
revolutionary council
A revolutionary council is a governing or decision-making body formed during a revolution to coordinate actions, direct political change, and often assume or challenge state authority.
-
B.
coup committee
A coup committee is a small, often clandestine group of military, political, or security elites that plans, coordinates, and directs the overthrow of an existing government.
-
C.
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.
-
D.
revolutionary parliament
A revolutionary parliament is a legislative body formed during or after a revolution to represent the new political order, draft foundational laws or constitutions, and legitimize transformative changes in governance.
-
E.
revolutionary society
A revolutionary society is a social organization or community fundamentally structured around initiating, supporting, or institutionalizing radical political, economic, or cultural change that breaks sharply from existing systems.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:23 p.m.