Triple

T13922539
Position Surface form Disambiguated ID Type / Status
Subject Shulgi of Ur E334781 entity
Predicate father P120 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: [Shulgi of Ur, father, Ur-Nammu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ur-Nammu
Context triple: [Shulgi of Ur, father, 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. Ur-Nammur
    Ur-Nammur is an alternate spelling of Ur-Nammu, the Sumerian king of Ur who founded the Third Dynasty of Ur and issued one of the earliest known law codes.
  • D. Lugal Kish
    Lugal Kish is an ancient Mesopotamian royal title denoting the king or ruler of the city-state of Kish, often associated with early Sumerian hegemony.
  • E. Sargon
    Sargon is the main antagonist, a ruthless and power-hungry warrior, in the fantasy action film "The Scorpion King 2: Rise of a Warrior."
  • 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_69d81c5f739081908bc05b2461f54828 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2aa5c1f481908a9d8786872f08fe completed April 14, 2026, 11:53 a.m.
NED1 Entity disambiguation (via context triple) batch_69fba1c45ba4819096233570d8d4afec completed May 6, 2026, 8:17 p.m.
Created at: April 9, 2026, 10:16 p.m.