Triple
T25119785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarascan military |
E629234
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | institution of the Purépecha state |
C49743
|
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: institution of the Purépecha state Context triple: [Tarascan military, instanceOf, institution of the Purépecha state]
-
A.
highland Maya state
A highland Maya state is a politically centralized society in the mountainous regions of the Maya area, characterized by hierarchical governance, urban centers, intensive agriculture, and complex religious and economic institutions.
-
B.
pre-Columbian polity
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.
-
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.
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.
-
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. chosen
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_69e2ff3288048190bd82c3b7f7bd0e62 |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:27 a.m.