Triple
T18012376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congress of Apatzingán |
E430914
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | revolutionary legislative assembly |
C1656
|
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 legislative assembly Context triple: [Congress of Apatzingán, instanceOf, revolutionary legislative assembly]
-
A.
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.
-
B.
revolutionary congress
chosen
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.
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.
-
D.
provisional legislative body
A provisional legislative body is a temporary lawmaking assembly established to exercise legislative authority during a transitional or interim period before a permanent government structure is formed or restored.
-
E.
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.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:24 a.m.