Triple
T7660126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bidesia theatre |
E173483
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bhojpuri theatre form |
C22373
|
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: Bhojpuri theatre form Context triple: [Bidesia theatre, instanceOf, Bhojpuri theatre form]
-
A.
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.
-
B.
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.
-
C.
Punjabi folk tale
A Punjabi folk tale is a traditional narrative from the Punjab region that conveys cultural values, humor, and moral lessons through stories of everyday people, legendary heroes, and supernatural beings.
-
D.
Kashmiri Pandit festival
A Kashmiri Pandit festival is a traditional religious and cultural celebration observed by the Kashmiri Pandit community, marked by specific rituals, prayers, and customs rooted in Kashmiri Shaivism and local heritage.
-
E.
regional variety of Odia
A regional variety of Odia is a geographically localized form of the Odia language characterized by distinct phonological, lexical, and sometimes grammatical features shared by speakers in a particular area.
- 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_69c69955517c819085bc715b96d304d2 |
completed | March 27, 2026, 2:51 p.m. |
Created at: March 27, 2026, 3:59 p.m.