Triple

T16608052
Position Surface form Disambiguated ID Type / Status
Subject Nakai Misl E403494 entity
Predicate hasNotableMember P304 FINISHED
Object Ran Singh Nakai E1239200 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: Ran Singh Nakai | Statement: [Nakai Misl, hasNotableMember, Ran Singh Nakai]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ran Singh Nakai
Context triple: [Nakai Misl, hasNotableMember, Ran Singh Nakai]
  • A. Ran Singh Nakai chosen
    Ran Singh Nakai was an 18th-century Sikh chieftain who ruled the Nakai Misl, one of the prominent Sikh confederacies in the Punjab region.
  • B. Gyan Singh Nakai
    Gyan Singh Nakai was a Sikh chieftain who led the Nakai Misl, one of the prominent Sikh confederacies in 18th-century Punjab.
  • C. Bhagwan Singh Nakai
    Bhagwan Singh Nakai was a prominent Sikh leader who headed the Nakai Misl, one of the principal confederacies of the 18th-century Sikh Misls in Punjab.
  • D. Man Singh
    Man Singh was an Indian noble and close associate of Nana Sahib who played a role in the events of the 1857 Indian Rebellion.
  • E. 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.
  • 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_69d883880d0c81908b5fcd454e767b60 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e36093901881909b85af47f75879a9 completed April 18, 2026, 10:44 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00dbf6507081909f6a49c003f9d6d6 completed May 10, 2026, 7:26 p.m.
Created at: April 10, 2026, 5:17 a.m.