Triple

T17951332
Position Surface form Disambiguated ID Type / Status
Subject Dyaus Pitar E448837 entity
Predicate nameElement P27866 FINISHED
Object Dyaus NE NERFINISHED

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: Dyaus | Statement: [Dyaus Pitar, nameElement, Dyaus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dyaus
Context triple: [Dyaus Pitar, nameElement, Dyaus]
  • A. Dyaus Pitar chosen
    Dyaus Pitar is the ancient Vedic sky god, regarded as a primordial father figure and etymological cognate of the Greek Zeus and Roman Jupiter.
  • B. Vivasvan
    Vivasvan is a Vedic epithet of the Hindu sun god, revered as a solar deity and progenitor of humanity in ancient Indian scriptures.
  • C. Indra
    Indra is the king of the gods and lord of storms, war, and the heavens in ancient Vedic and Hindu mythology.
  • D. Svarga
    Svarga is the heavenly realm in Hindu cosmology, ruled by the god Indra and inhabited by gods and righteous souls.
  • E. Purushottama Deva
    Purushottama Deva was a prominent 15th-century king of Odisha known for expanding the Gajapati Empire and patronizing the Jagannath cult and temple architecture.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9f8cca8819099836916c56b7c95 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4afac95048190a5d1ef012899c62b completed April 19, 2026, 10:34 a.m.
Created at: April 10, 2026, 10:21 a.m.