Triple

T22591120
Position Surface form Disambiguated ID Type / Status
Subject Hindu pantheon E564951 entity
Predicate hasDeity P5606 FINISHED
Object Indra 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: Indra | Statement: [Hindu pantheon, hasDeity, Indra]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Indra
Context triple: [Hindu pantheon, hasDeity, Indra]
  • A. Indra chosen
    Indra is the king of the gods and lord of storms, war, and the heavens in ancient Vedic and Hindu mythology.
  • 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. Rudra
    Rudra is a fierce and storm-associated Vedic deity later identified with the Hindu god Shiva, known for his destructive and healing powers.
  • D. Dyaus Pitar
    Dyaus Pitar is the ancient Vedic sky god, regarded as a primordial father figure and etymological cognate of the Greek Zeus and Roman Jupiter.
  • E. Vishrava
    Vishrava is a revered sage in Hindu mythology, best known as the father of the demon king Ravana and his giant brother Kumbhakarna in the Ramayana.
  • 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_69e245836014819091b91ed3074742a3 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f16160651081909d23735336fd7a16 completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 2:48 p.m.