Triple

T8925916
Position Surface form Disambiguated ID Type / Status
Subject Ur-Nammu E212538 entity
Predicate instanceOf P0 FINISHED
Object Sumerian king C24141 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: Sumerian king
Context triple: [Ur-Nammu, instanceOf, Sumerian king]
  • A. Kayanian king
    A Kayanian king is the sovereign ruler of the ancient Kayanian dynasty, embodying divine authority, martial prowess, and the cultural ideals of his realm.
  • B. ancient Near Eastern ruler chosen
    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.
  • C. Neo-Babylonian king
    A Neo-Babylonian king is the sovereign ruler of the Neo-Babylonian Empire (c. 626–539 BCE), responsible for military leadership, monumental building projects, religious patronage, and the administration of law and tribute across Mesopotamia.
  • D. Hittite king
    A Hittite king is the supreme political, military, and religious ruler of the Hittite Empire, responsible for governing the state, leading armies, conducting diplomacy, and performing key religious rituals to maintain divine favor and social order.
  • E. Kushite king
    A Kushite king is a sovereign ruler of the ancient Nubian kingdom of Kush, often governing from cities like Napata or Meroë and at times ruling over Egypt as a pharaoh during the 25th Dynasty.
  • 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_69ca839481d48190b42b037e0d0f636c completed March 30, 2026, 2:07 p.m.
Created at: March 30, 2026, 6:57 p.m.