Triple
T25693570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maru-Gurjara |
E644259
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional style of Indian architecture |
C821
|
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: regional style of Indian architecture Context triple: [Maru-Gurjara, instanceOf, regional style of Indian architecture]
-
A.
Indian art style
Indian art style is a diverse visual tradition characterized by intricate patterns, symbolic motifs, vibrant colors, and regionally distinct forms that reflect the subcontinent’s religious, cultural, and historical narratives.
-
B.
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.
-
C.
Islamic architecture style
Islamic architecture style is a design tradition characterized by geometric patterns, calligraphy, domes, arches, courtyards, and intricate ornamentation that reflect Islamic cultural, religious, and aesthetic principles.
-
D.
architectural style
chosen
An architectural style is a distinctive set of design principles, forms, materials, and decorative elements that characterize the built works of a particular period, region, culture, or movement.
-
E.
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.
- 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:31 p.m.