Triple
T5048141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texcoco |
E113717
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Aztec Triple Alliance |
C6681
|
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: member of the Aztec Triple Alliance Context triple: [Texcoco, instanceOf, member of the Aztec Triple Alliance]
-
A.
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.
-
B.
Aztec ruler
An Aztec ruler was the supreme political, military, and religious leader of the Aztec Empire, responsible for governing the state, leading armies, overseeing tribute, and serving as an intermediary with the gods.
-
C.
tlatoani of Tenochtitlan
The tlatoani of Tenochtitlan was the supreme ruler and political, military, and religious leader of the Mexica (Aztec) capital city-state, governing its affairs and representing its authority within the broader Aztec Empire.
-
D.
Aztec emperor
An Aztec emperor is the supreme political, military, and religious ruler of the Aztec Empire, responsible for governing the state, leading armies, overseeing tribute, and serving as the primary intermediary between the gods and the people.
-
E.
pre-Columbian city-state
chosen
A pre-Columbian city-state is an autonomous urban-centered political entity in the Americas that existed before European contact, typically comprising a primary city and its surrounding territories, governed by its own ruling elite, institutions, and cultural traditions.
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:37 p.m.