Triple
T31092368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of 1836 of Mexico |
E792423
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mexican constitutional charter |
C57217
|
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 constitutional charter Context triple: [Constitution of 1836 of Mexico, instanceOf, Mexican constitutional charter]
-
A.
foundational charter of Mexico
chosen
The foundational charter of Mexico is the core constitutional document that establishes the nation's fundamental principles, governmental structure, and the rights and obligations of its people.
-
B.
ley de la República de Colombia
Una "ley de la República de Colombia" es una norma jurídica de carácter general y obligatorio, expedida por el Congreso de la República y sancionada por el Presidente, que regula aspectos fundamentales de la vida social, económica y política del país.
-
C.
Francoist fundamental law
A Francoist fundamental law was one of the quasi-constitutional statutes enacted under Francisco Franco’s dictatorship in Spain that collectively structured and legitimized the regime’s political and institutional order.
-
D.
Mexican pronunciamiento
A Mexican pronunciamiento is a formal, often military-led political declaration that publicly rejects the existing government or policies and calls for specific changes or a new regime.
-
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.
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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:02 p.m.