Triple
T26143030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mukteswara Temple |
E659574
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kalinga architecture monument |
C51167
|
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: Kalinga architecture monument Context triple: [Mukteswara Temple, instanceOf, Kalinga architecture monument]
-
A.
Maya monument
A Maya monument is a large, often intricately carved architectural or sculptural structure created by the ancient Maya civilization to commemorate rulers, deities, historical events, or cosmological beliefs.
-
B.
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.
-
C.
Pallava-era monument
A Pallava-era monument is an ancient South Indian architectural structure, typically rock-cut or structural, built under the Pallava dynasty and characterized by intricate carvings, Dravidian temple forms, and early experiments in stone architecture.
-
D.
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.
-
E.
Wari archaeological site
The Wari archaeological site is the remains of an ancient Andean urban and ceremonial center associated with the Wari civilization, featuring complex architecture, administrative compounds, and evidence of early imperial organization in pre-Inca Peru.
- 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_69ee5bc496a88190af7deb7ab5e081de |
completed | April 26, 2026, 6:39 p.m. |
Created at: April 26, 2026, 8:21 p.m.