Triple

T7787893
Position Surface form Disambiguated ID Type / Status
Subject Veeragase E187292 entity
Predicate associatedDeity P1481 FINISHED
Object Veerabhadra E580797 NE FINISHED

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: Veerabhadra | Statement: [Veeragase, associatedDeity, Veerabhadra]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Veerabhadra
Context triple: [Veeragase, associatedDeity, Veerabhadra]
  • A. Narasimha
    Narasimha is the fierce man-lion incarnation of the Hindu god Vishnu, known for destroying the demon king Hiranyakashipu to protect his devotee Prahlada.
  • B. Vighneshvara
    Vighneshvara is a prominent form of the Hindu god Ganesha, revered as the remover of obstacles and patron of beginnings and wisdom.
  • C. Vrushabhadri
    Vrushabhadri is one of the sacred hills of the Tirumala range associated with the Tirumala Venkateswara Temple in Andhra Pradesh, India.
  • D. Mahadeva chosen
    Mahadeva is a principal form of the Hindu god Shiva, revered as the supreme deity and great lord in Shaivism.
  • E. Parashurama
    Parashurama is the warrior-sage incarnation of the Hindu god Vishnu, famed for wielding an axe and for his role in purging corrupt Kshatriya rulers.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69ca82af2d2c8190963861f5e0b8bf21 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cae7e779ec8190b77296d9c2ac3210 completed March 30, 2026, 9:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69caf61f77808190a5a1814fe1cb7ae1 completed March 30, 2026, 10:15 p.m.
Created at: March 30, 2026, 4:24 p.m.