Triple

T13474255
Position Surface form Disambiguated ID Type / Status
Subject Parminder Jawanda E318209 entity
Predicate hasChild P369 FINISHED
Object Rajpal Jawanda E1046536 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: Rajpal Jawanda | Statement: [Parminder Jawanda, hasChild, Rajpal Jawanda]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rajpal Jawanda
Context triple: [Parminder Jawanda, hasChild, Rajpal Jawanda]
  • A. Jaswant Jawanda chosen
    Jaswant Jawanda is an individual known primarily as the child of Parminder Jawanda.
  • B. Jagmal Singh
    Jagmal Singh was a 16th-century Rajput prince of Mewar, known as the disputed successor of Maharana Udai Singh II and for later serving under the Mughal Empire.
  • C. 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.
  • D. Beant Singh
    Beant Singh was one of the Sikh bodyguards who assassinated Indian Prime Minister Indira Gandhi in 1984.
  • E. Baldev Singh
    Baldev Singh was an Indian Sikh political leader who became the first Defence Minister of independent India and played a key role in the country’s transition during and after Partition.
  • 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_69d806b6bfec819089222715b2e86c8e completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaf2447bc81908baf1f4b55095144 completed April 12, 2026, 2:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69f76ba344e0819098da09416a913851 completed May 3, 2026, 3:37 p.m.
Created at: April 9, 2026, 9:42 p.m.