Triple

T15758837
Position Surface form Disambiguated ID Type / Status
Subject Zimri-Lim E382039 entity
Predicate father P120 FINISHED
Object Yahdun-Lim E1162224 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: Yahdun-Lim | Statement: [Zimri-Lim, father, Yahdun-Lim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yahdun-Lim
Context triple: [Zimri-Lim, father, Yahdun-Lim]
  • A. Yahdun-Lim chosen
    Yahdun-Lim was an early 2nd-millennium BCE king of the ancient Mesopotamian city-state of Mari, known from royal inscriptions and diplomatic correspondence.
  • B. Zimri-Lim
    Zimri-Lim was an early 18th-century BCE Amorite king of Mari in Mesopotamia, known from extensive palace archives that illuminate the politics and society of his time.
  • 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. 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.
  • E. Amar-Sin
    Amar-Sin was a king of the Third Dynasty of Ur in ancient Mesopotamia, known for his extensive building projects and efforts to consolidate and expand his 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_69d86d9e6b44819085d1f6a969ecb74c completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e050b35ea48190a758ee76a57b5451 completed April 16, 2026, 3 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffe4670e8881908bc9f3879ba208ba completed May 10, 2026, 1:50 a.m.
Created at: April 10, 2026, 4:47 a.m.