Triple

T7123823
Position Surface form Disambiguated ID Type / Status
Subject Sri Ranganathaswamy Temple, Srirangam E166009 entity
Predicate hasShrine P15258 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: [Sri Ranganathaswamy Temple, Srirangam, hasShrine, Hanuman]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hanuman
Context triple: [Sri Ranganathaswamy Temple, Srirangam, hasShrine, 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 major Hindu deity and the virtuous prince-king of Ayodhya, revered as the seventh avatar of Vishnu and hero of the epic Ramayana.
  • 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_69c6888350588190870cd552b427a1cd completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e64ab1f881908bc2468cc72d2544 completed March 27, 2026, 8:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7ad899dc081908808dc60015fd19e completed March 28, 2026, 10:29 a.m.
Created at: March 27, 2026, 2:44 p.m.