Triple

T2817357
Position Surface form Disambiguated ID Type / Status
Subject Khaldoon E54319 entity
Predicate hasVariantSpelling P457 FINISHED
Object Khaldoun E54319 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: Khaldoun | Statement: [Khaldoon, hasVariantSpelling, Khaldoun]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Khaldoun
Context triple: [Khaldoon, hasVariantSpelling, Khaldoun]
  • A. Khaldun
    Khaldun is a male given name of Arabic origin, historically associated with the famous Muslim historian and philosopher Ibn Khaldun.
  • B. Khaldoon chosen
    Khaldoon is an Arabic masculine given name commonly used in the Middle East.
  • C. Sahnun
    Sahnun was a prominent 9th-century Islamic jurist from North Africa whose compilation of legal opinions, the Mudawwana, became a foundational text of the Maliki school of Sunni jurisprudence.
  • D. Al-Hareeq
    Al-Hareeq is a town in central Saudi Arabia known for its agricultural activity, particularly date palm cultivation, within the Riyadh region.
  • E. Lakhdar
    Lakhdar is an Arabic masculine given name most notably borne by Algerian diplomat Lakhdar Brahimi.
  • 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_69ab49de0af08190b3da69683be1e728 completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abde500d3c8190b435a20a0f9d3b9d completed March 7, 2026, 8:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69afe8b344ec8190948b26a5101fb183 completed March 10, 2026, 9:47 a.m.
Created at: March 6, 2026, 9:59 p.m.