Triple

T9779128
Position Surface form Disambiguated ID Type / Status
Subject Ninurta E237320 entity
Predicate equatedWith P6530 FINISHED
Object Ningirsu E237320 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: Ningirsu | Statement: [Ninurta, equatedWith, Ningirsu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ningirsu
Context triple: [Ninurta, equatedWith, Ningirsu]
  • A. Ninurta chosen
    Ninurta is a Mesopotamian god associated with war, hunting, and agriculture, often depicted as a heroic warrior and champion of the god Enlil.
  • B. Enlil
    Enlil is a chief god in ancient Mesopotamian religion, associated with wind, air, and authority over the cosmos.
  • C. Enmerkar
    Enmerkar is a legendary Sumerian king of Uruk, best known from ancient Mesopotamian epics that depict his rivalries, quests, and early developments in writing and civilization.
  • D. Enlil-nirari
    Enlil-nirari was a Middle Assyrian king who ruled the Assyrian Empire in the 14th century BCE, helping to consolidate its growing regional power.
  • 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_69ca84d975a08190aab25b02a89bdab3 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cda13663f081909b95563038eb6485 completed April 1, 2026, 10:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69dbac7a42348190a86fa5a97e3d36ca completed April 12, 2026, 2:30 p.m.
Created at: March 30, 2026, 8:27 p.m.