Triple
T25230445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pallava architecture |
E632206
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | South Indian architecture |
C20598
|
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 architecture Context triple: [Pallava architecture, instanceOf, South Indian architecture]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
temple architecture
chosen
Temple architecture is the conceptual class encompassing the design principles, structural elements, symbolic forms, and spatial organization used to create sacred buildings for worship across different cultures and historical periods.
-
E.
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.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
Created at: April 21, 2026, 1:04 p.m.