Triple

T35782235
Position Surface form Disambiguated ID Type / Status
Subject Luwian religion E1034465 entity
Predicate instanceOf P0 FINISHED
Object Anatolian religion C18218 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: Anatolian religion
Context triple: [Luwian religion, instanceOf, Anatolian religion]
  • A. ancient Near Eastern religion
    Ancient Near Eastern religion encompasses the diverse, interconnected religious beliefs, rituals, and mythologies of civilizations such as Sumer, Akkad, Babylonia, Assyria, Canaan, and Israel from the Bronze and Iron Ages.
  • B. Anatolian deity chosen
    An Anatolian deity is a divine figure worshiped in the ancient regions of Anatolia, embodying local religious beliefs, natural forces, or societal roles within the mythologies of cultures such as the Hittites, Luwians, and Phrygians.
  • C. ancient Anatolian polities
    Ancient Anatolian polities were the diverse city-states, kingdoms, and empires that arose in the region of Anatolia (modern-day Turkey), including powers such as the Hittites, Lydians, Phrygians, and others, which played key roles in the political and cultural dynamics of the ancient Near East and Mediterranean.
  • D. goddess cult
    A goddess cult is a religious or spiritual group devoted to the worship, veneration, and ritual celebration of one or more female deities, often emphasizing themes of fertility, nature, power, and divine femininity.
  • E. Roman cult
    A Roman cult is a religious group or practice in ancient Rome centered on the worship of a specific deity, emperor, or sacred concept, involving prescribed rituals, offerings, and communal observances.
  • 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_69f76e14a1e081908eddd57bd6fdb3be completed May 3, 2026, 3:47 p.m.
Created at: May 3, 2026, 4:06 p.m.