Triple
T26061957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bit-Adini |
E657283
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Near Eastern polity |
C36515
|
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: ancient Near Eastern polity Context triple: [Bit-Adini, instanceOf, ancient Near Eastern polity]
-
A.
ancient Anatolian polities
Ancient Anatolian polities were the diverse city-states, kingdoms, and empires that arose in the region of Anatolia (modern-day Turkey), including powers such as the Hittites, Lydians, Phrygians, and others, which played key roles in the political and cultural dynamics of the ancient Near East and Mediterranean.
-
B.
ancient Near Eastern dynasty
An ancient Near Eastern dynasty is a succession of rulers from the same family or lineage that governed a state or empire in the Near East during antiquity, shaping its political, cultural, and religious development over time.
-
C.
Syro-Aramean polity
chosen
A Syro-Aramean polity is a historical or conceptual political entity rooted in the cultural, linguistic, and territorial interplay of ancient Syrian and Aramean societies in the Near East.
-
D.
Elamite polity
An Elamite polity is a socio-political entity of ancient Elam, characterized by its own governing structures, territorial domain, and cultural identity within the broader Elamite civilization.
-
E.
historical polities
Historical polities are organized political entities or governing structures that existed in the past, such as kingdoms, empires, city-states, and federations, defined by their territorial control, institutions, and sociopolitical systems.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 7:18 p.m.