Triple

T8030957
Position Surface form Disambiguated ID Type / Status
Subject Simon Singh E186975 entity
Predicate familyName P18 FINISHED
Object Singh E94257 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: Singh | Statement: [Simon Singh, familyName, Singh]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Singh
Context triple: [Simon Singh, familyName, Singh]
  • A. Singh chosen
    Singh is a common Indian surname used across various regions and communities, often associated with warriors, nobility, and particularly with Sikh and Rajput heritage.
  • B. 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.
  • C. Akali Phula Singh
    Akali Phula Singh was a prominent Sikh warrior-monk and military leader renowned for his bravery and key role in expanding and defending the Sikh Empire in the early 19th century.
  • D. Sohan Singh Bhakna
    Sohan Singh Bhakna was an Indian revolutionary leader best known as a founding figure of the Ghadar movement against British colonial rule.
  • E. Dhillon
    Dhillon is a common Punjabi surname associated with a prominent Jat clan found primarily in northern India and the Punjabi diaspora.
  • 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_69ca82ae2d1081909dbfee42b41db419 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3eef921081908d0ea21f142c175a completed March 31, 2026, 3:26 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc56e812dc81908916fc7163ae344a completed March 31, 2026, 11:21 p.m.
Created at: March 30, 2026, 5:22 p.m.