Triple
T14095599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achaemenid satrapy of Babylonia |
E339246
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Achaemenid satrapy |
C26239
|
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: Achaemenid satrapy Context triple: [Achaemenid satrapy of Babylonia, instanceOf, Achaemenid satrapy]
-
A.
Achaemenid province
chosen
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.
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.
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.
-
E.
Eyalet
An Eyalet is a major administrative division of the Ottoman Empire, governed by a beylerbey and comprising several subordinate districts or sanjaks.
- 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:22 p.m.