Triple

T23035188
Position Surface form Disambiguated ID Type / Status
Subject Muhammad Azam Shah E573574 entity
Predicate nobleRank P914 FINISHED
Object Shahzada NE NERFINISHED

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: [Muhammad Azam Shah, nobleRank, Shahzada]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shahzada
Context triple: [Muhammad Azam Shah, nobleRank, 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. Zahir
    Zahir is a given name of Arabic origin meaning "shining," "radiant," or "evident," used across various cultures as a masculine first or middle name.
  • D. Dunyazad
    Dunyazad is a character in the collection of Middle Eastern folk tales known as One Thousand and One Nights, traditionally depicted as the younger sister of Scheherazade.
  • E. Khushal
    Khushal is a male given name of Persian origin commonly used in South Asia, meaning "happy" or "prosperous."
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e245b911188190bc3d96326c847969 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1850df7fc81909ee522d99d96af0d completed April 29, 2026, 4:11 a.m.
Created at: April 17, 2026, 3:53 p.m.