Triple

T7824125
Position Surface form Disambiguated ID Type / Status
Subject Ashraf E181202 entity
Predicate hasVariant P455 FINISHED
Object Ashraf (Urdu form) E181202 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: Ashraf (Urdu form) | Statement: [Ashraf, hasVariant, Ashraf (Urdu form)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ashraf (Urdu form)
Context triple: [Ashraf, hasVariant, Ashraf (Urdu form)]
  • A. Ashraf chosen
    Ashraf is a masculine given name of Arabic origin commonly used in various Muslim-majority countries.
  • B. Ashfaq
    Ashfaq is the given name of Ashfaqulla Khan, an Indian freedom fighter and revolutionary associated with the Hindustan Republican Association during the struggle against British rule.
  • C. Zafar
    Zafar was an important ancient South Arabian city that served as the political and cultural center of the Himyarite Kingdom in what is now Yemen.
  • D. Zafar
    Zafar was the pen name of Bahadur Shah II, the last Mughal emperor of India and a noted Urdu poet.
  • E. Sharif
    Sharif is an honorific title in the Islamic world traditionally denoting a noble person descended from the Prophet Muhammad, particularly through the lineage of the Sayyids.
  • 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_69ca8282ccec819083c48efb72d21cf9 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cafa0abff08190b0245ceca5f20cae completed March 30, 2026, 10:32 p.m.
NED1 Entity disambiguation (via context triple) batch_69cb14aefd4881908ffa5825f4ba6eff completed March 31, 2026, 12:26 a.m.
Created at: March 30, 2026, 4:42 p.m.