Triple

T19896836
Position Surface form Disambiguated ID Type / Status
Subject Lasya E478172 entity
Predicate instanceOf P0 FINISHED
Object classical Indian 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: classical Indian dance style
Context triple: [Lasya, instanceOf, classical Indian dance style]
  • A. 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.
  • B. 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.
  • C. 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.
  • D. item in Indian classical performance
    An item in an Indian classical performance is a distinct, self-contained piece or segment—such as a composition, raga presentation, or dance number—structured with its own theme, mood, and form within the overall concert or recital.
  • E. 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.
  • 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_69d8e520682081909892916424699bd5 completed April 10, 2026, 11:55 a.m.
Created at: April 10, 2026, 1:52 p.m.