Triple
T28946891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gotipua |
E730604
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian folk dance |
C52850
|
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: Indian folk dance Context triple: [Gotipua, instanceOf, Indian folk dance]
-
A.
Indian dance
chosen
Indian dance is a diverse tradition of expressive movement and storytelling that encompasses classical, folk, and contemporary styles rooted in the cultural, spiritual, and regional histories of India.
-
B.
Punjabi folk dance
Punjabi folk dance is a vibrant, high-energy traditional dance form from the Punjab region, characterized by rhythmic footwork, expressive gestures, and colorful attire performed to lively folk music.
-
C.
Indian classical dance style
An Indian classical dance style is a traditional, codified form of dance originating from India that combines expressive storytelling, intricate rhythmic footwork, stylized gestures, and spiritual or mythological themes within a specific regional and cultural framework.
-
D.
Indian classical dance tradition
Indian classical dance tradition is a diverse system of highly codified, spiritually rooted performance forms that integrate expressive movement, rhythm, music, and storytelling to embody and transmit cultural, religious, and aesthetic values across generations.
-
E.
North Indian folk tradition
North Indian folk tradition encompasses the region’s diverse, community-based music, dance, storytelling, and ritual practices that express local histories, beliefs, and everyday life.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 8:40 a.m.