Triple

T5200250
Position Surface form Disambiguated ID Type / Status
Subject Bajrangbali E117375 entity
Predicate hasOtherName P39 FINISHED
Object Anjaneya E505609 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: Anjaneya | Statement: [Bajrangbali, hasOtherName, Anjaneya]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Anjaneya
Context triple: [Bajrangbali, hasOtherName, 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. 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.
  • D. Mrigadava
    Mrigadava is the ancient deer park near Sarnath in India where Gautama Buddha is said to have delivered his first sermon.
  • E. Karpagambal
    Karpagambal is the Hindu goddess Parvati worshipped as the consort of Lord Shiva at the Kapaleeshwarar Temple in Mylapore, Chennai.
  • 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_69bd4462ed04819084fcb01eb9d2fa74 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7a209d7c81908fa0d3bf2c482a34 completed March 20, 2026, 4:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69befe58344881908386713f2cf5749b completed March 21, 2026, 8:23 p.m.
Created at: March 20, 2026, 1:47 p.m.