Triple
T8779854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | morenada dance |
E208697
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bolivian folkloric dance |
C1135
|
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: Bolivian folkloric dance Context triple: [morenada dance, instanceOf, Bolivian folkloric 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.
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.
-
C.
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.
-
D.
Bolivian language
A Bolivian language is any natural language or officially recognized indigenous or colonial tongue that is historically spoken within the geographic and cultural boundaries of Bolivia.
-
E.
traditional dance
chosen
A traditional dance is a culturally rooted form of movement and expression passed down through generations, often performed during rituals, celebrations, or community gatherings to preserve and convey shared heritage and values.
- 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.