Triple
T12435416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revolutionary Command Council of Iraq |
E297131
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | supreme governing council |
C308
|
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: supreme governing council Context triple: [Revolutionary Command Council of Iraq, instanceOf, supreme governing council]
-
A.
governing council
chosen
A governing council is a formal body of appointed or elected individuals responsible for making high-level decisions, setting policies, and providing oversight for an organization, community, or institution.
-
B.
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.
-
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 committee
A revolutionary committee is a temporary governing or coordinating body formed during a revolution to organize, direct, and implement political, military, or social change against an existing regime.
-
E.
supreme soviet
The Supreme Soviet was the highest legislative body in the Soviet Union (and in its constituent republics), formally empowered to enact laws, approve plans and budgets, and elect key state officials, though in practice it largely ratified decisions made by the Communist Party leadership.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:55 p.m.