Triple

T18987686
Position Surface form Disambiguated ID Type / Status
Subject Anahita E464598 entity
Predicate instanceOf P0 FINISHED
Object Iranian deity C16283 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: Iranian deity
Context triple: [Anahita, instanceOf, Iranian deity]
  • A. Indo-Iranian deity chosen
    An Indo-Iranian deity is a divine figure originating from the shared religious and mythological traditions of the ancient Indo-Aryan and Iranian peoples, often associated with natural forces, social order, and cosmic principles.
  • B. 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.
  • C. ancient Iranian religion
    Ancient Iranian religion refers to the pre-Islamic religious beliefs and practices of the Iranian peoples, centered on a dualistic cosmology, reverence for deities like Ahura Mazda, and rituals that later influenced Zoroastrianism.
  • D. Ossetian deity
    An Ossetian deity is a divine figure from the traditional Ossetian (Scytho-Alanic) pantheon, embodying natural forces, social roles, or moral principles within the Ossetian mythological and religious worldview.
  • E. Urartian deity
    An Urartian deity is a divine figure worshiped in the ancient kingdom of Urartu, embodying aspects of nature, warfare, kingship, or fertility within the region’s polytheistic religious system.
  • 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_69d8dd008af48190a97ff1c6488edf1b completed April 10, 2026, 11:20 a.m.
Created at: April 10, 2026, 12:01 p.m.