Triple

T36375958
Position Surface form Disambiguated ID Type / Status
Subject al-Mustansir (Hafsid ruler) E895900 entity
Predicate instanceOf P0 FINISHED
Object Hafsid ruler C62544 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: Hafsid ruler
Context triple: [al-Mustansir (Hafsid ruler), instanceOf, Hafsid ruler]
  • A. Alaouite ruler
    An Alaouite ruler is a sovereign from the Alaouite dynasty of Morocco, which has governed the country since the 17th century, combining religious legitimacy as sharifs (descendants of the Prophet Muhammad) with political authority over the Moroccan state.
  • B. Muzaffarid ruler
    A Muzaffarid ruler is a sovereign or prince from the Muzaffarid dynasty that governed parts of Iran during the 14th century, exercising political, military, and administrative authority over its territories.
  • C. Aghlabid ruler
    An Aghlabid ruler is a sovereign from the Aghlabid dynasty who governed the semi-autonomous emirate of Ifriqiya under nominal Abbasid suzerainty, overseeing military expansion, economic development, and cultural patronage in North Africa and the central Mediterranean between the 9th and early 10th centuries.
  • D. Moroccan ruler
    A Moroccan ruler is a sovereign leader of Morocco, historically a sultan or king, who exercises political, religious, and symbolic authority over the state and its people.
  • E. Zengid ruler
    A Zengid ruler is a sovereign or governor from the Zengid dynasty, a 12th–13th century Muslim Turkic ruling house that controlled parts of Syria and northern Iraq, known for its military campaigns against Crusader states and efforts to unify Muslim territories.
  • F. None of above. chosen

Provenance (1 batch)

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_69f76e5115588190ad8738860b7bc68b completed May 3, 2026, 3:48 p.m.
Created at: May 3, 2026, 4:10 p.m.