Triple
T37301479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acolhua dynasty |
E925954
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mesoamerican dynasty |
C47517
|
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: Mesoamerican dynasty Context triple: [Acolhua dynasty, instanceOf, Mesoamerican dynasty]
-
A.
Maya royal dynasty
A Maya royal dynasty is a hereditary ruling lineage that governed a Maya city-state, legitimized its authority through divine ancestry, and oversaw political, religious, and military affairs across generations.
-
B.
Mesoamerican nobility
Mesoamerican nobility comprised the hereditary elite classes of pre-Columbian societies, who held political, religious, and military authority, controlled land and tribute, and maintained social hierarchy through lineage, ritual, and alliance.
-
C.
pre-Columbian city-state
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.
pre-Columbian polity
chosen
A pre-Columbian polity is a socially and politically organized group or state that existed in the Americas before European contact, characterized by its own systems of governance, economy, and culture.
-
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_69f76eb1bc508190924e9fa5d8acdeb3 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.