Triple
T7337098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revolutionary Command Council (Egypt) |
E169154
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | revolutionary governing council |
C11504
|
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 governing council Context triple: [Revolutionary Command Council (Egypt), instanceOf, revolutionary governing council]
-
A.
revolutionary council
chosen
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.
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.
-
C.
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.
-
D.
revolutionary state
A revolutionary state is a political entity formed and governed by a movement that has overthrown an existing regime, seeking to radically transform social, economic, and political structures according to its ideological goals.
-
E.
revolutionary court
A revolutionary court is a special judicial body established during periods of political upheaval to rapidly try and punish individuals deemed enemies of the revolution, often with limited legal safeguards.
- 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_69c68a568a6481908f11e20db7bc8446 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:04 p.m.