Triple

T8895583
Position Surface form Disambiguated ID Type / Status
Subject Ereshkigal E211797 entity
Predicate spouse P13 FINISHED
Object Nergal E196148 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: Nergal | Statement: [Ereshkigal, spouse, Nergal]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nergal
Context triple: [Ereshkigal, spouse, Nergal]
  • A. Nergal chosen
    Nergal is an ancient Mesopotamian god associated primarily with war, plague, and the underworld.
  • B. Marduk
    Marduk is the chief god of Babylon in ancient Mesopotamian religion, associated with creation, kingship, and the defeat of the chaos monster Tiamat.
  • C. Baal
    Baal is a prominent ancient Near Eastern storm and fertility god widely worshipped across Phoenician and Canaanite cultures.
  • D. Baal
    Baal is a 1918 expressionist play by Bertolt Brecht that follows the amoral, self-destructive life of a bohemian poet.
  • E. Nergal-šarra-uṣur
    Nergal-šarra-uṣur, better known by the Hellenized form Neriglissar, was a 6th-century BCE king of the Neo-Babylonian Empire who seized the throne after Nebuchadnezzar II’s son and ruled for a brief period marked by building projects and regional campaigns.
  • 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_69ca83918d3081909b326fa3750cb8c8 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc61be2c2081908f39cccdc149872d completed April 1, 2026, 12:07 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfac02974881908a7e8d9cfa47e624 completed April 3, 2026, 12:01 p.m.
Created at: March 30, 2026, 6:54 p.m.