Triple
T32117970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appan |
E820288
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | South Indian name element |
C6426
|
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 name element Context triple: [Appan, instanceOf, South Indian name element]
-
A.
South Indian surname
A South Indian surname is a family or lineage name originating from the southern states of India, often reflecting ancestral village, caste, profession, or linguistic community.
-
B.
Indian given name
chosen
An Indian given name is a personal name assigned at birth or during a naming ceremony in India, often reflecting linguistic, religious, cultural, or familial traditions.
-
C.
South Indian architectural style
South Indian architectural style is characterized by towering, intricately carved gopurams (gateway towers), pillared halls, and richly ornamented stone temples that emphasize verticality, rhythmic sculpture, and elaborate Dravidian iconography.
-
D.
South Indian festival
A South Indian festival is a culturally significant celebration rooted in the traditions, religions, and seasonal cycles of South India, marked by region-specific rituals, cuisine, music, dance, and community gatherings.
-
E.
South Indian tribal culture
South Indian tribal culture encompasses the diverse traditions, rituals, languages, art forms, and ecological knowledge systems of indigenous communities across the southern Indian states, shaped by deep connections to land, ancestry, and localized belief practices.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:28 a.m.