Triple

T8926147
Position Surface form Disambiguated ID Type / Status
Subject Ur III dynasty E212542 entity
Predicate hasRuler P5424 FINISHED
Object Shu-Sin E776967 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: Shu-Sin | Statement: [Ur III dynasty, hasRuler, Shu-Sin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shu-Sin
Context triple: [Ur III dynasty, hasRuler, Shu-Sin]
  • A. Shu-Sin chosen
    Shu-Sin was a king of the Third Dynasty of Ur in ancient Mesopotamia, known for his building projects and administrative reforms during the late 21st century BCE.
  • B. Samsu-iluna
    Samsu-iluna was a king of Babylon in the 18th century BCE, known for inheriting and struggling to maintain the vast empire established by his father Hammurabi.
  • C. Shamash-shum-ukin
    Shamash-shum-ukin was a 7th-century BCE Babylonian king, son of the Assyrian ruler Esarhaddon, best known for his ill-fated rebellion against his brother Ashurbanipal of Assyria.
  • D. Inshushinak
    Inshushinak is an ancient Elamite god associated with the city of Susa, often revered as a chief deity linked to justice, the underworld, and the protection of the state.
  • E. Enmerkar
    Enmerkar is a legendary Sumerian king of Uruk, best known from ancient Mesopotamian epics that depict his rivalries, quests, and early developments in writing and civilization.
  • 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_69ca839481d48190b42b037e0d0f636c completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc66700fb48190874563e535f20437 completed April 1, 2026, 12:27 a.m.
NED1 Entity disambiguation (via context triple) batch_69d19f50f1c4819099a9c511f58e9873 completed April 4, 2026, 11:31 p.m.
Created at: March 30, 2026, 6:57 p.m.