Triple
T25230446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pallava architecture |
E632206
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dravidian architecture |
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: Dravidian architecture Context triple: [Pallava architecture, instanceOf, Dravidian architecture]
-
A.
rock-cut architecture
Rock-cut architecture is a form of construction in which structures, spaces, and decorative elements are created by excavating and carving directly into natural rock formations rather than assembling them from separate building materials.
-
B.
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.
-
C.
Indian architectural treatise tradition
The Indian architectural treatise tradition comprises a corpus of Sanskrit and regional texts (śilpaśāstras, vāstuśāstras, and related manuals) that codify principles of design, proportion, ritual, and symbolism for constructing sacred and secular built environments.
-
D.
Indo-Saracenic style building
An Indo-Saracenic style building is a colonial-era architectural structure that fuses Indian, Islamic, and Gothic-Revival elements, often featuring domes, minarets, arches, and ornate decorative detailing.
-
E.
terracotta temple
A terracotta temple is a religious structure built primarily from baked clay tiles or bricks, often richly adorned with intricate sculptural reliefs and decorative motifs.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
Created at: April 21, 2026, 1:04 p.m.