Triple
T36769660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Council |
E908439
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | revolutionary government organ |
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 government organ Context triple: [Supreme Council, instanceOf, revolutionary government organ]
-
A.
revolutionary institution
A revolutionary institution is an organized structure or body that emerges or is transformed during periods of radical social or political upheaval to challenge, replace, or fundamentally reshape existing systems of power and governance.
-
B.
local organ of state power
A local organ of state power is a governmental body operating at the subnational level that exercises state authority and administers public affairs within a defined local territory in accordance with national law.
-
C.
Provisional government
A provisional government is a temporary governing authority established to manage a state during a transitional period, typically following the collapse of a previous regime or before the creation of a permanent political system.
-
D.
governmental organization
A governmental organization is a formally structured public entity established by a government to create, implement, or enforce laws, policies, and services for a specific jurisdiction or public purpose.
-
E.
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.
- 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.