Triple

T15586122
Position Surface form Disambiguated ID Type / Status
Subject Shahzada Parviz Mirza E374625 entity
Predicate title P38 FINISHED
Object Shahzada E379611 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: Shahzada | Statement: [Shahzada Parviz Mirza, title, Shahzada]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shahzada
Context triple: [Shahzada Parviz Mirza, title, Shahzada]
  • A. Shahzada chosen
    Shahzada is a royal title used in Persianate and South Asian cultures to denote a prince or son of a monarch.
  • B. Mirza
    Mirza is a historical noble title of Persian and Central Asian origin, commonly borne by princes and high-ranking members of royal and aristocratic families.
  • C. Khushal
    Khushal is a male given name of Persian origin commonly used in South Asia, meaning "happy" or "prosperous."
  • D. Shamsher
    Shamsher is the given first name of legendary Indian film actor and director Shammi Kapoor, a major star of Hindi cinema’s golden era.
  • E. Azeem-O-Shaan Shahenshah
    "Azeem-O-Shaan Shahenshah" is a grand, celebratory Bollywood song from the historical epic film *Jodhaa Akbar*, known for its lavish choreography and regal depiction of Emperor Akbar’s court.
  • 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_69d85ccd575081908909b71a3f3e3a61 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04e4900408190aadb48b001db4169 completed April 16, 2026, 2:49 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff5f33310881908dd509c2ab2822ac completed May 9, 2026, 4:22 p.m.
Created at: April 10, 2026, 4:11 a.m.