Triple

T8877477
Position Surface form Disambiguated ID Type / Status
Subject Tonk State E211322 entity
Predicate titleOfRuler P10605 FINISHED
Object Nawab E161924 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: Nawab | Statement: [Tonk State, titleOfRuler, Nawab]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nawab
Context triple: [Tonk State, titleOfRuler, Nawab]
  • A. Nawab chosen
    Nawab is a traditional aristocratic title historically used in South Asia for powerful Muslim rulers and chieftains, often associated with regional governance, landownership, and hereditary leadership.
  • B. Nawabzada
    Nawabzada is an honorific title traditionally used in South Asia to denote the son or descendant of a nawab, a hereditary noble or ruler.
  • C. Nawab Bai
    Nawab Bai was a Mughal empress and consort of Emperor Aurangzeb (Alamgir I), known as the mother of his successor Bahadur Shah I.
  • D. Nawab of Dhaka
    The Nawab of Dhaka was the hereditary aristocratic title of the leading Muslim noble family of Dhaka, historically influential in the politics and society of Bengal under British rule.
  • E. Nawab of Bihar
    The Nawab of Bihar was a hereditary Mughal-era noble title denoting the semi-autonomous ruler of the Bihar region in eastern India.
  • 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_69ca838e78748190934d82db3104f855 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc61496870819097c55c73aca62aac completed April 1, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfabaf57b88190a71d5303767ab517 completed April 3, 2026, 11:59 a.m.
Created at: March 30, 2026, 6:52 p.m.