Triple
T22850241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ras Lila |
E566337
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Manipuri classical dance form |
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: Manipuri classical dance form Context triple: [Ras Lila, instanceOf, Manipuri classical dance form]
-
A.
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.
-
B.
Indian classical dance style
chosen
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.
-
C.
Bhojpuri theatre form
Bhojpuri theatre form is a regional dramatic tradition from the Bhojpuri-speaking areas of India and Nepal that blends folk music, dance, and storytelling to depict local life, social issues, and cultural values.
-
D.
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.
-
E.
Balinese dance
Balinese dance is a traditional Indonesian performing art from Bali characterized by intricate hand gestures, expressive facial movements, and dynamic body postures that narrate stories from mythology and daily 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:36 p.m.