Triple
T20402988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andean ritual calendar |
E500384
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Andean cultural practice |
C11741
|
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 cultural practice Context triple: [Andean ritual calendar, instanceOf, Andean cultural practice]
-
A.
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.
-
B.
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.
-
C.
Andean deity
An Andean deity is a divine figure revered in the indigenous cosmologies of the Andes, embodying natural forces, ancestral spirits, and social order within highland communities.
-
D.
Peruvian celebration
chosen
A Peruvian celebration is a culturally rich festivity that blends Indigenous, Spanish, and Afro-Peruvian traditions through music, dance, food, and religious or civic rituals to honor historical events, saints, agricultural cycles, or community identity.
-
E.
Andean language
An Andean language is any of the indigenous languages historically spoken in the Andean region of South America, such as Quechua and Aymara, characterized by rich agglutinative morphology and deep cultural significance.
- 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:29 a.m.