Triple
T21725306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coya of the Inca Empire |
E536259
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Inca institution |
C45205
|
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: Inca institution Context triple: [Coya of the Inca Empire, instanceOf, Inca institution]
-
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.
Inca imperial policy
Inca imperial policy was a centralized system of governance that combined military conquest, forced resettlement, standardized administration, and state-managed economy and religion to integrate diverse Andean peoples under the authority of the Sapa Inca.
-
C.
pre-Columbian Mesoamerican institution
A pre-Columbian Mesoamerican institution is an organized social, political, religious, or economic structure—such as a temple complex, marketplace, or governing council—that regulated and shaped communal life in Mesoamerican societies before European contact.
-
D.
Inca cultural artifact
An Inca cultural artifact is a tangible object created or used by the Inca civilization that reflects their social structure, religious beliefs, technological skills, and artistic traditions.
-
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. 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:48 p.m.