Triple

T15703356
Position Surface form Disambiguated ID Type / Status
Subject Shamshi-Adad I E380647 entity
Predicate builtOrDevelopedCity P63973 FINISHED
Object Assur E40938 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: Assur | Statement: [Shamshi-Adad I, builtOrDevelopedCity, Assur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Assur
Context triple: [Shamshi-Adad I, builtOrDevelopedCity, Assur]
  • A. Ashur chosen
    Ashur is an ancient Mesopotamian city in northern Iraq that served as the first capital and religious center of the Assyrian Empire.
  • B. Ashur
    Ashur is the principal deity of the ancient Assyrian pantheon, associated with kingship, war, and the identity of the Assyrian state.
  • C. Esagila
    Esagila was the principal temple complex dedicated to the god Marduk in ancient Babylon, serving as a major religious and ceremonial center of Mesopotamia.
  • D. Shuruppak
    Shuruppak was an important ancient Sumerian city in southern Mesopotamia, traditionally associated with early urban development and the Sumerian flood myth.
  • E. Amel-Marduk
    Amel-Marduk was a 6th-century BCE king of Babylon, known from biblical and cuneiform sources as the successor of Nebuchadnezzar II and for releasing the Judean king Jehoiachin from prison.
  • 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_69d86d9bf930819082b30cf6d169297c completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e142df48e8819083a48d3b7b3f7f5d completed April 16, 2026, 8:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69ff87631854819084c20a335119dfcc completed May 9, 2026, 7:13 p.m.
Created at: April 10, 2026, 4:45 a.m.