Triple
T33887712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tikal–Calakmul rivalry |
E868673
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Maya political rivalry |
C19756
|
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: Maya political rivalry Context triple: [Tikal–Calakmul rivalry, instanceOf, Maya political rivalry]
-
A.
Mesoamerican war
Mesoamerican war is a conceptual class encompassing the organized, often ritualized armed conflicts among pre-Columbian Mesoamerican societies, characterized by distinctive military practices, religious motivations, and sociopolitical objectives.
-
B.
dynastic rivalry
chosen
Dynastic rivalry is the sustained political, military, and familial competition between ruling houses or lineages for supremacy, legitimacy, and control over territories or thrones.
-
C.
conflict in New Spain
Conflict in New Spain refers to the social, political, economic, and cultural struggles among Indigenous peoples, Spanish authorities, settlers, and mixed populations that shaped colonial life and power relations in the Viceroyalty of New Spain.
-
D.
intra-state rivalry
Intra-state rivalry is a sustained, competitive relationship between distinct political, social, or armed actors operating within the same state who contest authority, resources, or legitimacy.
-
E.
Mesoamerican alliance
A Mesoamerican alliance is a political and military coalition formed between pre-Columbian Mesoamerican city-states or polities to coordinate warfare, trade, tribute, and regional dominance.
- 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:48 a.m.