Triple

T19815093
Position Surface form Disambiguated ID Type / Status
Subject Namakkal E476038 entity
Predicate hasTempleDeity P83903 FINISHED
Object Lord Narasimha 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: Lord Narasimha | Statement: [Namakkal, hasTempleDeity, Lord Narasimha]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lord Narasimha
Context triple: [Namakkal, hasTempleDeity, Lord 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. Nrisimhadeva
    Nrisimhadeva is the fierce half-man, half-lion incarnation of the Hindu god Vishnu, revered as a powerful protector of devotees.
  • 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 (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_69d8e51bc4208190a1c57d8c5d1b15e4 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e654f861248190a633dd8d227d9697 completed April 20, 2026, 4:31 p.m.
Created at: April 10, 2026, 1:50 p.m.