Triple

T20305973
Position Surface form Disambiguated ID Type / Status
Subject Anjaneya E505609 entity
Predicate hasName P744 FINISHED
Object Anjaneya 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: Anjaneya | Statement: [Anjaneya, hasName, Anjaneya]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Anjaneya
Context triple: [Anjaneya, hasName, Anjaneya]
  • A. Anjaneya chosen
    Anjaneya is another name for the Hindu deity Hanuman, revered as a symbol of strength, devotion, and selfless service.
  • B. 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.
  • C. Simhavishnu
    Simhavishnu was an early and influential Pallava king in South India, known for consolidating Pallava power in the Tamil region and patronizing art and architecture that laid the groundwork for later Pallava achievements.
  • D. Balarama
    Balarama is a major Hindu deity revered as the elder brother of Krishna, known for his immense strength and role in supporting and protecting dharma.
  • E. Banasura
    Banasura is a powerful asura king in Hindu mythology, best known for his thousand arms and his battle with Krishna over his daughter Usha.
  • 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_69e0b4b8ab648190906e18538c250148 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6773f8f688190b616f972b9bbb28e completed April 20, 2026, 6:58 p.m.
Created at: April 16, 2026, 11:18 a.m.