Triple

T10691143
Position Surface form Disambiguated ID Type / Status
Subject Assyrian religion E252010 entity
Predicate pantheonIncludes P13203 FINISHED
Object Marduk E38028 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: Marduk | Statement: [Assyrian religion, pantheonIncludes, Marduk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Marduk
Context triple: [Assyrian religion, pantheonIncludes, Marduk]
  • A. Marduk chosen
    Marduk is the chief god of Babylon in ancient Mesopotamian religion, associated with creation, kingship, and the defeat of the chaos monster Tiamat.
  • B. Labashi-Marduk
    Labashi-Marduk was a short-reigning Neo-Babylonian king, likely the son of Neriglissar, who was overthrown in a conspiracy soon after ascending the throne in the 6th century BCE.
  • C. Ninurta
    Ninurta is a Mesopotamian god associated with war, hunting, and agriculture, often depicted as a heroic warrior and champion of the god Enlil.
  • D. 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.
  • E. Nergal
    Nergal is an ancient Mesopotamian god associated primarily with war, plague, and the underworld.
  • 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_69d6aa5bd7c08190a816e733b4045c23 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6fd3705788190bcbdef93b4c5f574 completed April 9, 2026, 1:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69e2161018408190bcb64efba0974f8c completed April 17, 2026, 11:14 a.m.
Created at: April 8, 2026, 9:11 p.m.