Triple
T2858802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinchaysuyu |
E63267
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | region of the Inca Empire |
C11793
|
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: region of the Inca Empire Context triple: [Chinchaysuyu, instanceOf, region of the Inca Empire]
-
A.
Incan citadel
An Incan citadel is a fortified highland complex of stone-built structures, terraces, and ceremonial spaces that served as a political, religious, and military center of the Inca civilization.
-
B.
Andean chronological period
An Andean chronological period is a defined span of time used by archaeologists and historians to organize and interpret the cultural, political, and technological development of societies in the Andean region of South America.
-
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.
Andean culture
Andean culture encompasses the diverse traditions, social structures, and belief systems developed by indigenous peoples of the Andes, characterized by highland agriculture, intricate textiles, communal organization, and deep spiritual ties to the mountainous landscape.
-
E.
Inca ruler
An Inca ruler was the supreme political, religious, and military leader of the Inca Empire, believed to be a divine descendant of the sun god Inti and responsible for governing its vast territories and people.
- 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_69ab4c41e8c08190a9e8f5249cc12610 |
completed | March 6, 2026, 9:50 p.m. |
Created at: March 6, 2026, 10:02 p.m.