Triple

T8926142
Position Surface form Disambiguated ID Type / Status
Subject Ur III dynasty E212542 entity
Predicate mainDeity P7648 FINISHED
Object Enlil E37112 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: Enlil | Statement: [Ur III dynasty, mainDeity, Enlil]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Enlil
Context triple: [Ur III dynasty, mainDeity, Enlil]
  • A. Enlil chosen
    Enlil is a chief god in ancient Mesopotamian religion, associated with wind, air, and authority over the cosmos.
  • B. Ninurta
    Ninurta is a Mesopotamian god associated with war, hunting, and agriculture, often depicted as a heroic warrior and champion of the god Enlil.
  • 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. Enki
    Enki is a major Sumerian god associated with water, wisdom, creation, and magic, often depicted as a benefactor of humanity and a master of divine knowledge.
  • E. Adad-happe
    Adad-happe was a Neo-Babylonian queen, known primarily as the wife of King Nabopolassar and mother of his royal heirs.
  • 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_69ca839481d48190b42b037e0d0f636c completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc66700fb48190874563e535f20437 completed April 1, 2026, 12:27 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2571ac8ec8190bf59c2cec5e2e6e2 completed April 5, 2026, 12:35 p.m.
Created at: March 30, 2026, 6:57 p.m.