Triple
T16471667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sasanian Iberia |
E400077
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sasanian province |
C37493
|
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 province Context triple: [Sasanian Iberia, instanceOf, Sasanian province]
-
A.
Achaemenid province
An Achaemenid province is an administrative region within the Achaemenid Persian Empire, governed by a satrap or local authority responsible for taxation, security, and implementing imperial policies.
-
B.
Assyrian province
An Assyrian province is an administrative territorial unit of the ancient Assyrian Empire, governed by an appointed official responsible for taxation, military conscription, and local order under the authority of the Assyrian king.
-
C.
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.
-
D.
province of Iran
A province of Iran is a primary administrative division of the country, governed by a centrally appointed governor and encompassing multiple counties, cities, and rural districts.
-
E.
province of the Abbasid Caliphate
A province of the Abbasid Caliphate is an administrative territorial unit governed by a caliphal-appointed official responsible for local governance, tax collection, security, and implementation of central policies within the empire.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:11 a.m.