Triple

T4930801
Position Surface form Disambiguated ID Type / Status
Subject Hanuman Jayanti E110689 entity
Predicate honorsDeity P5606 FINISHED
Object Hanuman E21412 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: Hanuman | Statement: [Hanuman Jayanti, honorsDeity, Hanuman]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hanuman
Context triple: [Hanuman Jayanti, honorsDeity, Hanuman]
  • A. Hanuman chosen
    Hanuman is a revered Hindu deity known for his immense strength, unwavering devotion to Lord Rama, and central role in the epic Ramayana.
  • B. Hanuman Pol
    Hanuman Pol is one of the main historic entrance gates of Rajasthan’s Kumbhalgarh Fort, serving as a fortified access point and defensive structure.
  • C. Rama
    Rama is a small scenic village in Pakistan’s Gilgit-Baltistan region, known as a gateway to the lush Rama Meadows and views of Nanga Parbat.
  • D. Rama
    Rama is a major Hindu deity and the virtuous prince-king of Ayodhya, revered as the seventh avatar of Vishnu and hero of the epic Ramayana.
  • E. 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.
  • 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_69bd4415190c8190817bee7ec9f9f944 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd706245e48190a61d573438461c30 completed March 20, 2026, 4:05 p.m.
NED1 Entity disambiguation (via context triple) batch_69be9c44e91881909513a679886cbdef completed March 21, 2026, 1:25 p.m.
Created at: March 20, 2026, 1:30 p.m.