Triple
T18776904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tlaxcalan leadership |
E459154
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pre-Columbian polity leadership |
C21369
|
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: pre-Columbian polity leadership Context triple: [Tlaxcalan leadership, instanceOf, pre-Columbian polity leadership]
-
A.
pre-Columbian ruler
chosen
A pre-Columbian ruler is a sovereign leader who governed a society or state in the Americas before the arrival of Christopher Columbus and subsequent European colonization.
-
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.
precolonial ruler
A precolonial ruler is a sovereign leader who governed a territory or people before the establishment of formal colonial rule, exercising political, military, economic, and often spiritual authority within indigenous systems of power.
-
D.
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.
-
E.
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.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:52 a.m.