Triple
T31034483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Agustín de Iturbide’s government |
E790818
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mexican Empire government |
C59572
|
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: Mexican Empire government Context triple: [Emperor Agustín de Iturbide’s government, instanceOf, Mexican Empire government]
-
A.
monarch of Mexico
A monarch of Mexico is the sovereign ruler who holds the highest hereditary or elected authority over the Mexican state and its people during a monarchical period.
-
B.
institution of the Purépecha state
An institution of the Purépecha state is a formal political, religious, military, or economic organization that structured governance, social order, and resource management within the pre-Hispanic Purépecha polity.
-
C.
Mexican royalty
Mexican royalty refers to the historical and often symbolic noble lineages and ruling families associated with Mexico’s pre-Hispanic empires and colonial-era monarchy, whose titles and influence have largely become ceremonial or cultural in modern times.
-
D.
Aztec military order
An Aztec military order was an elite, hierarchically organized warrior society within the Aztec Empire, whose members earned status and privileges through battlefield achievements and played key roles in warfare, politics, and religious ceremonies.
-
E.
Mexican political plan
A Mexican political plan is a formal, often revolutionary, document that outlines a political movement’s principles, goals, and strategies for restructuring or challenging the existing government in Mexico.
- 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:59 p.m.