Triple
T22773185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palace of Khosrow I |
E563613
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sasanian palace |
C46806
|
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: Sasanian palace Context triple: [Palace of Khosrow I, instanceOf, Sasanian palace]
-
A.
Byzantine imperial palace
A Byzantine imperial palace is a grand, fortified residential and ceremonial complex that housed the emperor and court, combining administrative, religious, and domestic functions in richly decorated architectural spaces.
-
B.
Umayyad desert palace
An Umayyad desert palace is an early Islamic rural complex, often located in arid or steppe regions, combining residential, administrative, agricultural, and sometimes defensive and bathhouse functions for Umayyad elites.
-
C.
Sasanian rock relief
A Sasanian rock relief is a large-scale stone carving, typically on cliff faces or rock walls, created during the Sasanian Empire to depict royal ceremonies, victories, and religious scenes as expressions of imperial power and ideology.
-
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.
Achaemenid architecture
Achaemenid architecture is the monumental building style of the first Persian Empire, characterized by grand palatial complexes, tall stone columns, elaborate reliefs, and a synthesis of Mesopotamian, Egyptian, and Anatolian influences.
- 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_69e24554497c819080b996e071de27c2 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:27 p.m.