Triple
T22518945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naqsh-e Rajab |
E556722
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sasanian rock relief |
C46451
|
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 rock relief Context triple: [Naqsh-e Rajab, instanceOf, Sasanian rock relief]
-
A.
Sasanian royal inscription
A Sasanian royal inscription is an official monumental text commissioned by Sasanian kings, typically carved on rock faces, buildings, or artifacts, proclaiming their titles, achievements, religious affiliations, and political authority.
-
B.
Assyrian palace reliefs
Assyrian palace reliefs are intricately carved stone panels that decorated royal Assyrian palaces, depicting military campaigns, hunting scenes, religious rituals, and courtly life to glorify the king’s power and divine authority.
-
C.
Achaemenid inscription
An Achaemenid inscription is a formal text carved or written on durable materials during the Achaemenid Empire, typically in multiple languages and scripts, to record royal proclamations, commemorations, or religious dedications.
-
D.
Achaemenid art collection
A curated assemblage of artworks, artifacts, and decorative objects produced under the Achaemenid Empire, reflecting its imperial ideology, cross-cultural influences, and distinctive aesthetic styles.
-
E.
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.
- 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:50 p.m.