Triple
T13962231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elamite kingdom of Anshan |
E335824
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Elamite polity |
C34429
|
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: Elamite polity Context triple: [Elamite kingdom of Anshan, instanceOf, Elamite polity]
-
A.
Sumerian dynasty
A Sumerian dynasty is a succession of rulers from the same family or lineage who governed a Sumerian city-state or region in ancient Mesopotamia.
-
B.
Arabian polity
An Arabian polity is a political entity or state structure that governs a defined territory and population within the Arabian Peninsula or broader Arab world, shaped by regional history, culture, and power relations.
-
C.
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.
-
D.
ancient Iranian dynasty
An ancient Iranian dynasty is a long-ruling hereditary line of monarchs originating in the Iranian cultural sphere that governed significant territories in antiquity, shaping the region’s political, social, and religious history.
-
E.
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.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:18 p.m.