Triple
T25693472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dravida |
E644257
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | South Indian architectural style |
C50645
|
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: South Indian architectural style Context triple: [Dravida, instanceOf, South Indian architectural style]
-
A.
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.
-
B.
South Indian royal dynasty
A South Indian royal dynasty is a hereditary ruling family that governed regions of southern India, shaping its political structures, culture, religion, and art over successive generations.
-
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.
South Indian kingdom
A South Indian kingdom is a historically or culturally defined political entity located in the southern part of the Indian subcontinent, characterized by distinct Dravidian languages, traditions, and regional governance.
-
E.
South Indian dynasty
A South Indian dynasty is a long-standing ruling lineage or family that governed regions of southern India, shaping its political history, culture, religion, and art over successive generations.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 8:31 p.m.