Triple

T6541291
Position Surface form Disambiguated ID Type / Status
Subject Nawab of Orissa E168293 entity
Predicate hasTitle P38 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: [Nawab of Orissa, hasTitle, Nawab]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nawab
Context triple: [Nawab of Orissa, hasTitle, 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_69c68a51564081909e93aee0dbd9cca3 completed March 27, 2026, 1:46 p.m.
NER Named-entity recognition batch_69c6add7369c8190919cd7c07012a994 completed March 27, 2026, 4:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6d53edf108190b74098b41c143a65 completed March 27, 2026, 7:06 p.m.
Created at: March 27, 2026, 1:50 p.m.