Triple

T21293961
Position Surface form Disambiguated ID Type / Status
Subject Jhujhar Singh E524867 entity
Predicate name P16 FINISHED
Object Jhujhar Singh 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: Jhujhar Singh | Statement: [Jhujhar Singh, name, Jhujhar Singh]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jhujhar Singh
Context triple: [Jhujhar Singh, name, Jhujhar Singh]
  • A. Jhujhar Singh chosen
    Jhujhar Singh was a 17th-century Bundela Rajput ruler of Orchha in central India, known for his conflicts with the Mughal Empire during Shah Jahan’s reign.
  • B. Jagdanand Singh
    Jagdanand Singh is an Indian politician and senior leader of the Rashtriya Janata Dal, known for his long-standing role in Bihar state politics.
  • C. Beant Singh
    Beant Singh was one of the Sikh bodyguards who assassinated Indian Prime Minister Indira Gandhi in 1984.
  • D. Satwant Singh
    Satwant Singh was one of the Sikh bodyguards who assassinated Indian Prime Minister Indira Gandhi in 1984, an event that triggered widespread anti-Sikh riots across India.
  • E. Malkhan Singh
    Malkhan Singh is a former notorious dacoit from India’s Chambal ravines who later gained prominence for surrendering and entering public life.
  • 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_69e0b517e6748190850d6f6ddf323d69 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e73856ba988190a8359efecea362cc completed April 21, 2026, 8:41 a.m.
Created at: April 16, 2026, 4:04 p.m.