Triple
T34148055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chakyar Koothu |
E875917
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hindu temple art |
C40161
|
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: Hindu temple art Context triple: [Chakyar Koothu, instanceOf, Hindu temple art]
-
A.
Hindu religious artwork
Hindu religious artwork comprises visual representations—such as paintings, sculptures, and carvings—that depict Hindu deities, myths, symbols, and rituals to inspire devotion and convey spiritual teachings.
-
B.
Buddhist art
Buddhist art is a diverse body of visual and material creations—such as sculptures, paintings, architecture, and ritual objects—designed to express, teach, and venerate the principles, stories, and figures of Buddhism across different cultures and historical periods.
-
C.
Hindu-Buddhist icon
A Hindu-Buddhist icon is a religious image or sculpture that visually represents deities, enlightened beings, or sacred concepts shared or syncretized between Hindu and Buddhist traditions, serving as a focus for devotion, meditation, and ritual.
-
D.
temple architecture
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.
Hindu temple ritual
chosen
A Hindu temple ritual is a structured sequence of sacred actions, chants, and offerings performed in a temple to honor deities, seek blessings, and maintain spiritual harmony between devotees and the divine.
- 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:54 a.m.