Triple

T23217829
Position Surface form Disambiguated ID Type / Status
Subject Mahadeva E580797 entity
Predicate alsoCalled P39 FINISHED
Object Rudra 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: Rudra | Statement: [Mahadeva, alsoCalled, Rudra]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rudra
Context triple: [Mahadeva, alsoCalled, Rudra]
  • A. Rudra chosen
    Rudra is a fierce and storm-associated Vedic deity later identified with the Hindu god Shiva, known for his destructive and healing powers.
  • B. Vritra
    Vritra is a powerful serpent or dragon-like demon in Hindu mythology, best known as the adversary slain by the god Indra to release the waters and restore cosmic order.
  • C. Indra
    Indra is the king of the gods and lord of storms, war, and the heavens in ancient Vedic and Hindu mythology.
  • D. Vrushabhadri
    Vrushabhadri is one of the sacred hills of the Tirumala range associated with the Tirumala Venkateswara Temple in Andhra Pradesh, India.
  • E. Sadyojata
    Sadyojata is one of the five faces of Lord Shiva, symbolizing creation and the westward aspect of the deity in Shaivite tradition.
  • 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_69e2460389408190be74f41d217799a9 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f1916653f08190a7dcbc659c6b6a25 completed April 29, 2026, 5:04 a.m.
Created at: April 17, 2026, 4:08 p.m.