Triple

T10327193
Position Surface form Disambiguated ID Type / Status
Subject P. V. Narasimha Rao E242789 entity
Predicate givenName P17 FINISHED
Object Narasimha E146684 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: Narasimha | Statement: [P. V. Narasimha Rao, givenName, Narasimha]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Narasimha
Context triple: [P. V. Narasimha Rao, givenName, Narasimha]
  • A. Narasimha chosen
    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. 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.
  • C. Anjaneya
    Anjaneya is another name for the Hindu deity Hanuman, revered as a symbol of strength, devotion, and selfless service.
  • D. Shanmukha
    Shanmukha is a revered Hindu deity of war and victory, widely worshipped as the six-faced son of Shiva and Parvati.
  • E. Gopala
    Gopala is a pastoral form of the Hindu god Krishna, revered especially as a divine cowherd and protector of cows.
  • 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_69d381af787481908bc401325c760a88 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d7ce69b881909f27d97c90643634 completed April 7, 2026, 10:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69d71dafa9308190ae0d3c34ba0c58b1 completed April 9, 2026, 3:31 a.m.
Created at: April 6, 2026, 11:51 a.m.