Triple
T33369988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shekhari Nagara |
E854461
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | substyle of Nagara architecture |
C50646
|
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: substyle of Nagara architecture Context triple: [Shekhari Nagara, instanceOf, substyle of Nagara architecture]
-
A.
sub-style of Nagara architecture
chosen
A sub-style of Nagara architecture is a regional or period-specific variation of the broader North Indian temple architectural tradition, distinguished by unique forms of shikhara, ornamentation, and layout while retaining core Nagara features.
-
B.
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.
-
C.
sub-temple
A sub-temple is a smaller, subsidiary shrine or sacred structure that exists within or under the administration of a larger main temple, often dedicated to a specific deity, ritual, or community function.
-
D.
Shingon subsect
A Shingon subsect is a branch within the esoteric Shingon school of Japanese Buddhism that maintains its own lineage, rituals, doctrinal emphases, and institutional organization while sharing core Shingon teachings.
-
E.
Chalukyan temple
A Chalukyan temple is a historic South Indian Hindu temple characterized by intricate stone carvings, star-shaped or multi-lobed plans, and a fusion of Nagara and Dravida architectural styles developed under the Chalukya dynasties.
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:35 a.m.