Triple
T15724489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babylonian kingship ideology |
E381187
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mesopotamian kingship ideology |
C33620
|
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: Mesopotamian kingship ideology Context triple: [Babylonian kingship ideology, instanceOf, Mesopotamian kingship ideology]
-
A.
royal ideology
chosen
Royal ideology is the set of beliefs, symbols, and narratives that justify and naturalize monarchical rule, defining the king or queen’s authority, legitimacy, and relationship to the divine and the governed.
-
B.
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.
-
C.
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.
-
D.
Mesopotamian royal epithet
A Mesopotamian royal epithet is a formal, often formulaic honorific phrase used in inscriptions and texts to define, praise, and legitimize a king’s divine favor, authority, and achievements.
-
E.
ancient Near Eastern ruler
An ancient Near Eastern ruler is a sovereign leader who governed a city-state or empire in regions such as Mesopotamia, Anatolia, the Levant, or Persia, wielding political, military, economic, and often religious authority.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:46 a.m.