Triple

T2101986
Position Surface form Disambiguated ID Type / Status
Subject Code of Ur-Nammu E37110 entity
Predicate creator P184 FINISHED
Object Ur-Nammu 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-Nammu | Statement: [Code of Ur-Nammu, creator, Ur-Nammu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ur-Nammu
Context triple: [Code of Ur-Nammu, creator, Ur-Nammu]
  • 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. 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.
  • C. Eannatum
    Eannatum was an early Sumerian king of Lagash known for his military conquests and one of the earliest recorded empires in Mesopotamian history.
  • D. 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.
  • E. Sargon of Akkad
    Sargon of Akkad was an ancient Mesopotamian king who founded the Akkadian Empire, often regarded as the world’s first great empire.
  • 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_69a8861828948190924aa30c08806b3a completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69abbabc83a8819091f786f21d33b5a6 completed March 7, 2026, 5:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae893779648190ae0d039c614736c8 completed March 9, 2026, 8:47 a.m.
Created at: March 4, 2026, 7:43 p.m.