Triple
T8197516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tututepec |
E191469
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mixtec polity |
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: Mixtec polity Context triple: [Tututepec, instanceOf, Mixtec polity]
-
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.
Inca polity
The Inca polity was a highly centralized, hierarchical imperial state in the Andes that integrated diverse ethnic groups through a complex system of administration, tribute, and state-sponsored religion centered on the Sapa Inca.
-
C.
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.
-
D.
Maya people
The Maya people are an indigenous Mesoamerican civilization known for their advanced writing system, mathematics, astronomy, and monumental architecture, with descendants who continue to maintain rich cultural traditions across present-day Mexico and Central America.
-
E.
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.
- 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_69ca82c6e9548190a4c5ca14516e4417 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:42 p.m.