Triple
T7348823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shah Mosque of Isfahan |
E169442
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Safavid-era monument |
C14344
|
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: Safavid-era monument Context triple: [Shah Mosque of Isfahan, instanceOf, Safavid-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.
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.
-
C.
16th-century mosque
chosen
A 16th-century mosque is an Islamic place of worship built in the 1500s, typically featuring domes, minarets, intricate geometric and calligraphic decoration, and reflecting the architectural styles of its regional Islamic empire.
-
D.
Zoroastrian funerary structure
A Zoroastrian funerary structure is a sacred architectural space, such as a tower of silence or charnel house, designed according to religious purity laws to expose or contain the dead without contaminating earth, fire, or water.
-
E.
imperial mosque
An imperial mosque is a grand, state-sponsored Islamic place of worship built or endowed by a ruling monarch or dynasty to serve both religious functions and symbolize political power and prestige.
- 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_69c68a5878888190968ce4d04db8d69f |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:05 p.m.