Triple

T19735752
Position Surface form Disambiguated ID Type / Status
Subject Alaeddin E473974 entity
Predicate givenName P17 FINISHED
Object Alaeddin 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: Alaeddin | Statement: [Alaeddin, givenName, Alaeddin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Alaeddin
Context triple: [Alaeddin, givenName, Alaeddin]
  • A. Alaeddin chosen
    Alaeddin was an early Ottoman statesman and son of Osman I, often regarded as the first Ottoman grand vizier.
  • B. Alaeddin Ali
    Alaeddin Ali was an Ottoman prince of the early 15th century, known primarily as a son of Sultan Murad II and a member of the Ottoman imperial dynasty.
  • C. Shahriyar
    Shahriyar was a Sasanian Persian prince, known primarily as the son of the last Sasanian king, Yazdegerd III.
  • D. Tāj al-Dīn
    Tāj al-Dīn is an honorific title meaning "Crown of the Religion," borne by the influential Egyptian Sufi scholar and spiritual master Ibn ‘Ata’ Allah al-Iskandari.
  • E. Pasha Qasim
    Pasha Qasim was an Ottoman military leader and provincial governor whose legacy is notably marked by the mosque bearing his name in Pécs, Hungary.
  • 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_69d8e517ebd48190979ee76723bcfadf completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6515ddea881909ea831b7bc16d934 completed April 20, 2026, 4:16 p.m.
Created at: April 10, 2026, 1:47 p.m.