Triple

T22508812
Position Surface form Disambiguated ID Type / Status
Subject Guru Ram Das E556460 entity
Predicate spouse P13 FINISHED
Object Bibi Bhani 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: Bibi Bhani | Statement: [Guru Ram Das, spouse, Bibi Bhani]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bibi Bhani
Context triple: [Guru Ram Das, spouse, Bibi Bhani]
  • A. Bibi Bhani chosen
    Bibi Bhani was a revered Sikh figure and daughter of Guru Amar Das, remembered for her devotion and pivotal role in supporting the early Sikh Gurus and the development of Amritsar.
  • B. Sachi Devi
    Sachi Devi was the wife of Jagannath Mishra, a noted Indian politician and former Chief Minister of Bihar.
  • C. Sachi Devi
    Sachi Devi is revered in Gaudiya Vaishnavism as the pious and devoted mother of the saint and religious reformer Chaitanya Mahaprabhu.
  • D. Harkha Bai
    Harkha Bai, better known by her royal title Mariam-uz-Zamani, was a Rajput princess who became a prominent Mughal empress as the wife of Emperor Akbar and mother of 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_69e11e555edc81909ca803587dafd747 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15d5ebe5881908a22d519128415f2 completed April 29, 2026, 1:22 a.m.
Created at: April 16, 2026, 8:50 p.m.