Triple

T8779806
Position Surface form Disambiguated ID Type / Status
Subject Diablada dance E208696 entity
Predicate instanceOf P0 FINISHED
Object traditional Andean folk dance C4252 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: traditional Andean folk dance
Context triple: [Diablada dance, instanceOf, traditional Andean folk dance]
  • A. Peruvian celebration
    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.
  • B. Andean culture chosen
    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.
  • C. Georgian folk dance
    Georgian folk dance is a traditional performing art from Georgia characterized by dynamic footwork, acrobatic movements, and expressive storytelling that reflects the country’s regional cultures and history.
  • D. traditional Mexican spectacle
    A traditional Mexican spectacle is a culturally rooted public performance or event—such as festivals, dances, rodeos, or religious celebrations—that combines music, costume, ritual, and communal participation to express and preserve Mexican heritage.
  • E. 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.
  • 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_69ca835fbee88190bf625939bac48d7f completed March 30, 2026, 2:06 p.m.
Created at: March 30, 2026, 6:42 p.m.