Triple
T31840497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumerian royal ideology |
E812789
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mesopotamian royal 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 royal ideology Context triple: [Sumerian royal ideology, instanceOf, Mesopotamian royal 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.
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.
-
C.
Assyrian royal inscription
An Assyrian royal inscription is a formal cuneiform text commissioned by an Assyrian king to record and glorify his military campaigns, building projects, piety, and divine legitimacy.
-
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.
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.
- 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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:49 p.m.