Triple
T19821406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vastu Shastra |
E476203
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian architectural treatise tradition |
C42660
|
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: Indian architectural treatise tradition Context triple: [Vastu Shastra, instanceOf, Indian architectural treatise tradition]
-
A.
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.
-
B.
Indian aesthetic theory
Indian aesthetic theory is a classical framework that explains how art and performance evoke refined emotional states (rasas) in the spectator through stylized expression, suggestion, and cultural convention.
-
C.
architectural journal
An architectural journal is a periodical publication that documents, analyzes, and critiques architectural works, theories, and practices for professionals, scholars, and enthusiasts in the field.
-
D.
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.
-
E.
architectural essay
An architectural essay is a reflective, often critical written work that analyzes buildings, spaces, or urban environments in relation to their design, function, cultural context, and experiential impact.
- F. None of above. chosen
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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:50 p.m.