Triple
T32359407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andean Middle Horizon |
E826818
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pre-Columbian cultural horizon |
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: pre-Columbian cultural horizon Context triple: [Andean Middle Horizon, instanceOf, pre-Columbian cultural horizon]
-
A.
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.
-
B.
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.
-
C.
pre-Columbian cultural area
A pre-Columbian cultural area is a geographically defined region of the Americas characterized by shared cultural, social, and technological traits among Indigenous societies prior to European contact.
-
D.
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.
-
E.
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.
- 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:49 a.m.