Triple
T12805933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaipur gharana |
E306143
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian classical dance style |
C31911
|
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 classical dance style Context triple: [Jaipur gharana, instanceOf, Indian classical dance style]
-
A.
Indian classical dancer
An Indian classical dancer is a performer trained in one or more traditional Indian dance forms, using codified gestures, expressions, and rhythmic movements to convey stories, emotions, and spiritual themes.
-
B.
South Indian art form
A South Indian art form is a traditional cultural expression from the southern regions of India, encompassing distinctive styles of dance, music, sculpture, painting, or craft that reflect local histories, religions, and aesthetics.
-
C.
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.
-
D.
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.
-
E.
South Indian classical music
South Indian classical music, or Carnatic music, is a highly structured and devotional musical tradition characterized by intricate melodic frameworks (ragas), complex rhythmic cycles (talas), and improvisation rooted in ancient Hindu scriptures and South Indian cultural heritage.
- F. None of above. chosen
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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:31 p.m.