Triple

T8916663
Position Surface form Disambiguated ID Type / Status
Subject Ur III period E212310 entity
Predicate hasMonarch P765 FINISHED
Object Ur-Namma E212538 NE FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Ur-Namma | Statement: [Ur III period, hasMonarch, Ur-Namma]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ur-Namma
Context triple: [Ur III period, hasMonarch, Ur-Namma]
  • A. Ur-Nammu chosen
    Ur-Nammu was an ancient Sumerian king of Ur best known for founding the Third Dynasty of Ur and issuing one of the earliest known law codes in history.
  • B. Eannatum
    Eannatum was an early Sumerian king of Lagash known for his military conquests and one of the earliest recorded empires in Mesopotamian history.
  • C. Rim-Sin I
    Rim-Sin I was a prominent Amorite king of Larsa in southern Mesopotamia, known for expanding his realm and briefly dominating much of Sumer in the early 2nd millennium BCE.
  • D. Lugalzagesi
    Lugalzagesi was a Sumerian king of Umma and later ruler of a briefly unified Sumer, known for his military conquests and eventual defeat by Sargon of Akkad.
  • E. Naram-Sin of Akkad
    Naram-Sin of Akkad was a powerful Mesopotamian king of the Akkadian Empire, famed for declaring himself a god and expanding the empire to its greatest territorial extent.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

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_69ca8393b1808190bd4336787ffa2c40 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc6610cd48819090a184c5f9465626 completed April 1, 2026, 12:25 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfdb83445c819085be0b13517292c9 completed April 3, 2026, 3:23 p.m.
Created at: March 30, 2026, 6:56 p.m.