Triple

T25693755
Position Surface form Disambiguated ID Type / Status
Subject Nagara Bhumija E644263 entity
Predicate instanceOf P0 FINISHED
Object Hindu temple architectural style 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 architectural style
Context triple: [Nagara Bhumija, instanceOf, Hindu temple architectural style]
  • 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 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.
  • C. Hindu temple group
    A Hindu temple group is a collection of Hindu temples, often located in close proximity, that together form a religious complex or pilgrimage center unified by shared deities, rituals, or historical and cultural significance.
  • D. Vijayanagara-period temple
    A Vijayanagara-period temple is a South Indian Hindu temple complex characterized by towering gopurams, pillared mandapas, intricate stone carvings, and a fortified, urban-like layout that flourished under the Vijayanagara Empire (14th–17th centuries).
  • E. Buddhist temple component
    A Buddhist temple component is an architectural or symbolic element—such as a hall, pagoda, gate, or altar—that contributes to the religious, ritual, and aesthetic functions of a Buddhist temple complex.
  • 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_69e77e82c9bc8190893090b2f6c64f1d completed April 21, 2026, 1:41 p.m.
Created at: April 21, 2026, 8:32 p.m.