Triple
T31197401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sassanian royal mints |
E795358
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of Sasanian imperial administration |
C60690
|
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: component of Sasanian imperial administration Context triple: [Sassanian royal mints, instanceOf, component of Sasanian imperial administration]
-
A.
Sasanian province
A Sasanian province was an administrative territorial unit of the Sasanian Empire, governed by appointed officials responsible for taxation, justice, and military organization within its boundaries.
-
B.
Achaemenid institution
An Achaemenid institution is an organized structure or system—political, administrative, religious, economic, or military—established and maintained by the Achaemenid Empire to govern, manage resources, and integrate its diverse territories.
-
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.
component of the Safavid Empire
A component of the Safavid Empire is any political, social, economic, military, religious, or cultural unit or institution that contributed to the structure, governance, and functioning of the Safavid state.
-
E.
Sasanian frontier stronghold
A Sasanian frontier stronghold is a fortified military installation positioned along the empire’s borders to control strategic routes, monitor enemy movements, and defend against incursions.
- 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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:09 p.m.