Triple

T8916486
Position Surface form Disambiguated ID Type / Status
Subject Ekur E212307 entity
Predicate associatedDeity P1481 FINISHED
Object Ninurta 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: Ninurta | Statement: [Ekur, associatedDeity, Ninurta]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ninurta
Context triple: [Ekur, associatedDeity, Ninurta]
  • 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. 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.
  • C. Marduk
    Marduk is the chief god of Babylon in ancient Mesopotamian religion, associated with creation, kingship, and the defeat of the chaos monster Tiamat.
  • D. Enlil
    Enlil is a chief god in ancient Mesopotamian religion, associated with wind, air, and authority over the cosmos.
  • E. Nabu
    Nabu is the Mesopotamian god of wisdom and writing, revered as the divine scribe and patron of scribes.
  • 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_69ca8393b1808190bd4336787ffa2c40 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc6610cd48819090a184c5f9465626 completed April 1, 2026, 12:25 a.m.
NED1 Entity disambiguation (via context triple) batch_69cffd8495488190a1d93f9e5b7e334d completed April 3, 2026, 5:48 p.m.
Created at: March 30, 2026, 6:56 p.m.