Triple

T8420577
Position Surface form Disambiguated ID Type / Status
Subject Sohain E198838 entity
Predicate hasAlternativeName P39 FINISHED
Object Sohaini (possible variant name) E198838 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: Sohaini (possible variant name) | Statement: [Sohain, hasAlternativeName, Sohaini (possible variant name)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sohaini (possible variant name)
Context triple: [Sohain, hasAlternativeName, Sohaini (possible variant name)]
  • A. Sohain chosen
    Sohain is a regional dialect of the Potohari language spoken in parts of the Potohar Plateau in Pakistan.
  • B. Sohi
    Sohi is a Punjabi-origin surname commonly found among people from the Indian subcontinent and their diaspora.
  • C. Singh
    Singh is a common Indian surname used across various regions and communities, often associated with warriors, nobility, and particularly with Sikh and Rajput heritage.
  • D. Sandhu
    Sandhu is a common Punjabi surname associated with a prominent Jat clan found mainly in northern India and Pakistan.
  • E. 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.
  • 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_69ca8312d63c8190bf133b676b44a385 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cb84ca7b348190abab25e79b05407f completed March 31, 2026, 8:24 a.m.
NED1 Entity disambiguation (via context triple) batch_69ce03476b288190b3df8f9f4d502ea8 completed April 2, 2026, 5:48 a.m.
Created at: March 30, 2026, 6:06 p.m.