Triple
T14491133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shikhara |
E359364
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hindu temple architecture feature |
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: Hindu temple architecture feature Context triple: [Shikhara, instanceOf, Hindu temple architecture feature]
-
A.
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.
-
B.
Hindu monastery
A Hindu monastery is a religious community and residence where Hindu monks live, study scriptures, practice spiritual disciplines, and guide devotees in accordance with specific traditions or lineages.
-
C.
Hindu monastic institution
A Hindu monastic institution is an organized religious community or center where renunciants (monks and nuns) live under spiritual discipline, pursue scriptural study, meditation, and service, and provide religious guidance to lay followers.
-
D.
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.
-
E.
temple
A temple is a dedicated sacred structure or space where individuals or communities engage in worship, rituals, and spiritual practices associated with a particular religion or belief system.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:20 a.m.