Triple
T15673722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gundeshapur |
E377384
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sasanian city |
C9491
|
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 city Context triple: [Gundeshapur, instanceOf, Sasanian city]
-
A.
Byzantine city
A Byzantine city is an urban center of the Eastern Roman (Byzantine) Empire characterized by fortified walls, Christian religious institutions, administrative and commercial hubs, and a blend of Greco-Roman and Eastern cultural influences.
-
B.
Sasanian client state
A Sasanian client state was a semi-autonomous polity that retained its own local rulers and internal administration while recognizing the suzerainty of the Sasanian Empire, often providing tribute, military support, and strategic buffer territory.
-
C.
Mesopotamian city
chosen
A Mesopotamian city is an ancient urban settlement characterized by organized streets, monumental temples (ziggurats), centralized administration, and irrigation-based agriculture along the Tigris and Euphrates rivers.
-
D.
Umayyad city
An Umayyad city is an urban center developed or significantly shaped under the Umayyad Caliphate (661–750 CE), characterized by early Islamic administrative, religious, and commercial functions integrated with existing local urban traditions.
-
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.
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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:16 a.m.