Triple
T12962187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Formative Horizon |
E321171
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Andean archaeological period |
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: Andean archaeological period Context triple: [Formative Horizon, instanceOf, Andean archaeological period]
-
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.
Pre-Columbian culture
Pre-Columbian culture encompasses the diverse societies, traditions, technologies, and belief systems that existed throughout the Americas before the arrival of Christopher Columbus and subsequent European contact.
-
E.
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.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 8:17 p.m.