Triple
T37088073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dadra (light classical) |
E918342
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hindustani semi-classical music form |
C61717
|
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: Hindustani semi-classical music form Context triple: [Dadra (light classical), instanceOf, Hindustani semi-classical music form]
-
A.
Indian classical music form
chosen
An Indian classical music form is a structured, traditional framework of melodic and rhythmic principles—such as raga and tala—used to compose, improvise, and perform music within the Hindustani or Carnatic systems.
-
B.
Hindustani classical music gharana
A Hindustani classical music gharana is a stylistically distinct lineage or school of musical thought and practice, traditionally passed down through generations of guru–shishya (teacher–disciple) relationships.
-
C.
Indian musical instrument
An Indian musical instrument is a traditional or contemporary device created and used within the Indian subcontinent to produce music, often reflecting the region’s cultural, spiritual, and stylistic diversity.
-
D.
Hindustani classical musician
A Hindustani classical musician is an artist who performs, improvises, and interprets North Indian classical music within established ragas and talas, often through vocal or instrumental traditions.
-
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.
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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.