Triple

T9197319
Position Surface form Disambiguated ID Type / Status
Subject Lugalzagesi E220748 entity
Predicate opponent P437 FINISHED
Object Urukagina E790960 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: Urukagina | Statement: [Lugalzagesi, opponent, Urukagina]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Urukagina
Context triple: [Lugalzagesi, opponent, Urukagina]
  • A. Urukagina chosen
    Urukagina was a Sumerian ruler of the city-state of Lagash, known for instituting some of the earliest recorded social and legal reforms in history.
  • B. Lugalbanda
    Lugalbanda is a heroic king of Uruk from Sumerian mythology, known both as a central figure in early epic tales and as the father of the legendary hero Gilgamesh.
  • C. Dūr-Šarrukīn
    Dūr-Šarrukīn was the Assyrian capital city founded by King Sargon II in the late 8th century BCE, renowned for its monumental palaces and reliefs.
  • D. 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.
  • E. Eannatum
    Eannatum was an early Sumerian king of Lagash known for his military conquests and one of the earliest recorded empires in Mesopotamian history.
  • 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_69ca83e7ba70819088b74866d9da2c30 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccd87f50e88190940e73af1deda747 completed April 1, 2026, 8:34 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1d58be8a4819088c419888a879e3e completed April 5, 2026, 3:22 a.m.
Created at: March 30, 2026, 7:25 p.m.