Triple
T3023753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Early Horizon |
E82527
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | chronological period in Andean prehistory |
C7881
|
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: chronological period in Andean prehistory Context triple: [Early Horizon, instanceOf, chronological period in Andean prehistory]
-
A.
Andean chronological period
chosen
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.
-
B.
pre-Columbian cultural period
A pre-Columbian cultural period is a span of time in the Americas before European contact, characterized by distinct indigenous societies, technologies, and belief systems.
-
C.
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.
-
D.
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.
-
E.
pre-Columbian city
A pre-Columbian city is a large, organized urban settlement in the Americas that existed before European contact, characterized by complex social, political, economic, and religious structures.
- 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3 p.m.