Triple
T9743900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rukmini Devi Arundale |
E236258
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian classical dancer |
C27201
|
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 dancer Context triple: [Rukmini Devi Arundale, instanceOf, Indian classical dancer]
-
A.
Russian ballet dancer
A Russian ballet dancer is a highly trained performer who embodies the rigorous technical precision, expressive artistry, and cultural traditions of Russia’s classical ballet heritage.
-
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.
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.
-
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.
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. 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_69ca84d3e24481908a476e2231123cf9 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:23 p.m.