Triple

T20096107
Position Surface form Disambiguated ID Type / Status
Subject Hidimba Devi Temple E496403 entity
Predicate namedAfter P63 FINISHED
Object Hidimba Devi 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: Hidimba Devi | Statement: [Hidimba Devi Temple, namedAfter, Hidimba Devi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hidimba Devi
Context triple: [Hidimba Devi Temple, namedAfter, Hidimba Devi]
  • A. Hidimba Devi chosen
    Hidimba Devi is a revered demoness-turned-goddess from the Indian epic Mahabharata, worshipped particularly in Himachal Pradesh.
  • B. Kalka Devi
    Kalka Devi is a revered Hindu goddess, worshipped as a powerful form of the Divine Mother associated with strength and protection.
  • C. Dharani Devi
    Dharani Devi is a goddess in Hindu mythology revered as the mother of Padmavati and associated with the nurturing, earth-like aspects of the divine feminine.
  • D. Manbhawati Bai
    Manbhawati Bai was a Mughal noblewoman best known as the mother of Prince Khusrau Mirza, the rebellious son of Emperor Jahangir.
  • E. Bilasa Devi
    Bilasa Devi is a legendary fisherwoman revered in the Bilaspur region of India, regarded as the folk heroine after whom the city is named.
  • 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_69da626eee3881909f3454986d4a6511 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6666cc02481908780a415b19c05a2 completed April 20, 2026, 5:46 p.m.
Created at: April 11, 2026, 11:25 p.m.