Triple
T14129905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kok Gumbaz Mosque |
E340134
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Timurid-era monument |
C26688
|
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: Timurid-era monument Context triple: [Kok Gumbaz Mosque, instanceOf, Timurid-era monument]
-
A.
Seljuk-era monument
A Seljuk-era monument is an architectural structure, such as a mosque, caravanserai, mausoleum, or fortress, built under Seljuk rule (11th–13th centuries) that exemplifies their distinctive Islamic art, engineering, and decorative styles.
-
B.
Timurid architectural ensemble
chosen
A Timurid architectural ensemble is a cohesive complex of buildings, spaces, and decorative elements that exemplifies the monumental scale, intricate ornamentation, and urban-planning principles characteristic of Timurid-era architecture.
-
C.
Mughal-era monument
A Mughal-era monument is a historic architectural structure built during the Mughal Empire, typically characterized by grand scale, intricate ornamentation, symmetrical design, and a blend of Persian, Islamic, and Indian styles.
-
D.
Qajar-era monument
A Qajar-era monument is a historical structure or commemorative edifice built or significantly modified during Iran’s Qajar dynasty (1789–1925), reflecting the period’s distinctive architectural, artistic, and cultural characteristics.
-
E.
Marinid-era monument
A Marinid-era monument is a historical structure or site built under the Marinid dynasty (13th–15th centuries) in North Africa, reflecting their distinctive Islamic architectural, political, and cultural legacy.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:23 p.m.