Triple

T19966640
Position Surface form Disambiguated ID Type / Status
Subject Nayef bin Abdullah E479951 entity
Predicate givenName P17 FINISHED
Object Nayef 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: Nayef | Statement: [Nayef bin Abdullah, givenName, Nayef]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nayef
Context triple: [Nayef bin Abdullah, givenName, Nayef]
  • A. Nayef chosen
    Nayef is a masculine given name of Arabic origin commonly used in the Arab world.
  • B. Nasir al-Sadoon
    Nasir al-Sadoon was an Iraqi statesman and tribal leader credited with establishing the city of Nasiriyah in southern Iraq.
  • C. Nayef bin Abdullah
    Nayef bin Abdullah was a Jordanian prince and son of King Abdullah I who briefly served as regent before being sidelined from the line of succession.
  • D. Al Anoud
    Al Anoud is a Saudi princess from the Al Jiluwi branch of the royal family, known primarily as the wife of King Fahd of Saudi Arabia.
  • E. Talal bin Muhammad
    Talal bin Muhammad is a Jordanian prince and senior member of the Hashemite royal family who has held various military and diplomatic roles.
  • 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_69d8e523c19881909f9197037200dde6 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65bc5e41881908c1e8867820f1c0c completed April 20, 2026, 5 p.m.
Created at: April 10, 2026, 1:54 p.m.