Triple
T30883997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Hittite Kingdom in Anatolia |
E786705
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hittite polity |
C7663
|
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: Hittite polity Context triple: [Old Hittite Kingdom in Anatolia, instanceOf, Hittite polity]
-
A.
Neo-Hittite kingdom
A Neo-Hittite kingdom is a small, Iron Age Syro-Anatolian state that emerged after the fall of the Hittite Empire, preserving and adapting Hittite cultural, political, and artistic traditions in a new regional context.
-
B.
Hittite institution
A Hittite institution is an organized social, political, religious, or legal structure within Hittite society that governed behavior, administration, and cultural practices in the Hittite civilization.
-
C.
Syro-Aramean polity
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.
ancient Anatolian polities
chosen
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.
-
E.
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.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:48 p.m.