Triple
T26062006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bit-Zamani |
E657284
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Syro-Mesopotamian state |
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: Syro-Mesopotamian state Context triple: [Bit-Zamani, instanceOf, Syro-Mesopotamian state]
-
A.
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.
-
B.
Canaanite city-state
A Canaanite city-state is an independent, fortified urban center in ancient Canaan that controlled its surrounding territory, governed by a local ruler and integrated into regional trade, diplomacy, and warfare.
-
C.
Mesopotamian city
A Mesopotamian city is an ancient urban settlement characterized by organized streets, monumental temples (ziggurats), centralized administration, and irrigation-based agriculture along the Tigris and Euphrates rivers.
-
D.
Semitic state
A Semitic state is a political entity historically or culturally rooted in Semitic-speaking peoples, characterized by shared linguistic, ethnic, and often religious traditions originating in the ancient Near East.
-
E.
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.
- 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.