Triple

T9075167
Position Surface form Disambiguated ID Type / Status
Subject Eannatum E217465 entity
Predicate reignedOver P10353 FINISHED
Object Lagash E212531 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: Lagash | Statement: [Eannatum, reignedOver, Lagash]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lagash
Context triple: [Eannatum, reignedOver, Lagash]
  • A. Lagash chosen
    Lagash was an important ancient Sumerian city-state in southern Mesopotamia, known for its early political power, distinctive art, and extensive cuneiform records.
  • B. Shuruppak
    Shuruppak was an important ancient Sumerian city in southern Mesopotamia, traditionally associated with early urban development and the Sumerian flood myth.
  • C. Nippur
    Nippur was an ancient Sumerian city in Mesopotamia that served as a major religious center dedicated to the god Enlil.
  • D. Eridu
    Eridu is an ancient Sumerian city often regarded as one of the world’s earliest urban centers and a significant religious and cultural hub in Mesopotamian civilization.
  • E. Harapha
    Harapha is a boastful Philistine giant who serves as Samson’s arrogant antagonist in John Milton’s tragic closet drama "Samson Agonistes."
  • 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_69ca83d6c14c8190bc056d927f00a2a2 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc95c4026c8190b553aedb9f4beabb completed April 1, 2026, 3:49 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1cc2ca7a081908f597e9a58920d6e completed April 5, 2026, 2:42 a.m.
Created at: March 30, 2026, 7:12 p.m.