Triple
T13630940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colla Kingdom |
E325715
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Aymara kingdom |
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: Aymara kingdom Context triple: [Colla Kingdom, instanceOf, Aymara kingdom]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
Wari site
A Wari site is an archaeological location associated with the Wari (Huari) civilization of the central Andes, characterized by planned urban centers, administrative compounds, and distinctive architectural and material culture remains dating roughly from 600–1000 CE.
-
E.
region of the Inca Empire
A region of the Inca Empire is a geographically defined administrative area governed by imperial officials to organize tribute, labor, and local affairs within the broader imperial structure.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:51 p.m.