Triple

T9705284
Position Surface form Disambiguated ID Type / Status
Subject Anjaneri Hills E234882 entity
Predicate associatedWithDeity P1481 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: [Anjaneri Hills, associatedWithDeity, Hanuman]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hanuman
Context triple: [Anjaneri Hills, associatedWithDeity, 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. Anjaneya
    Anjaneya is another name for the Hindu deity Hanuman, revered as a symbol of strength, devotion, and selfless service.
  • D. Rama
    Rama is a river in Bosnia and Herzegovina that flows through mountainous terrain before joining the Neretva River.
  • E. 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.
  • 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_69ca84cc78808190a56f3402b7c139a7 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9da369b4819081f6ce01289ed725 completed April 1, 2026, 10:35 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1af93b76c81908377f17956fb86b1 completed April 5, 2026, 12:40 a.m.
Created at: March 30, 2026, 8:18 p.m.