Triple

T32099313
Position Surface form Disambiguated ID Type / Status
Subject Atramhasis E819799 entity
Predicate instanceOf P0 FINISHED
Object MesopotamianMythologicalFigure C17299 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: MesopotamianMythologicalFigure
Context triple: [Atramhasis, instanceOf, MesopotamianMythologicalFigure]
  • A. Mesopotamian deity
    A Mesopotamian deity is a divine being from the ancient cultures of Sumer, Akkad, Assyria, and Babylonia, associated with specific cosmic, natural, or societal domains and worshiped through rituals, temples, and myths.
  • B. mythological figure
    A mythological figure is a legendary being or character from traditional stories and belief systems, often embodying cultural values, natural forces, or supernatural powers.
  • C. Mesopotamian legendary figure chosen
    A Mesopotamian legendary figure is a mythic or semi-divine personage from ancient Mesopotamian cultures whose stories, deeds, and attributes embody religious beliefs, moral values, and cosmological ideas preserved in epics, hymns, and ritual texts.
  • D. Babylonian god
    A Babylonian god is a divine being from ancient Mesopotamian religion, associated with specific cosmic functions, cities, or aspects of life, and worshiped through rituals, temples, and myths.
  • E. Mesopotamian mythological place
    A Mesopotamian mythological place is a legendary or sacred location from ancient Mesopotamian belief systems, such as heavens, underworlds, or divine cities, that features in myths, religious texts, and ritual narratives.
  • F. None of above.

Provenance (1 batch)

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_69f34901106881908ea893ad504a08be completed April 30, 2026, 12:20 p.m.
Created at: May 1, 2026, 12:26 a.m.