Triple

T37570087
Position Surface form Disambiguated ID Type / Status
Subject Alapini E934664 entity
Predicate instanceOf P0 FINISHED
Object Oyo Empire title C30798 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: Oyo Empire title
Context triple: [Alapini, instanceOf, Oyo Empire title]
  • A. Songhai monarch
    A Songhai monarch is the supreme hereditary ruler of the Songhai Empire, wielding centralized political, military, economic, and religious authority over its territories and subjects.
  • B. Yoruba monarch chosen
    A Yoruba monarch is a traditional hereditary ruler who embodies political authority, spiritual leadership, and cultural guardianship within a Yoruba kingdom or community.
  • C. Awori kingdom
    The Awori kingdom is a traditional Yoruba socio-political entity historically established by the Awori people in parts of present-day Lagos and Ogun States in southwestern Nigeria, characterized by its distinct cultural heritage, chieftaincy institutions, and urban settlements.
  • D. Mossi state
    The Mossi state refers to the centralized West African kingdoms founded by the Mossi people (notably Ouagadougou, Yatenga, and others in present-day Burkina Faso), characterized by hierarchical political structures, cavalry-based military power, and enduring resistance to external domination from the medieval period into the colonial era.
  • E. Jukun traditional state
    Jukun traditional state is a historical socio-political entity of the Jukun people in present-day Nigeria, characterized by centralized kingship, ritual authority, and a hierarchical system of governance rooted in indigenous customs and beliefs.
  • F. None of above.

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_69f76ecd99148190be327e391a70f5b6 completed May 3, 2026, 3:50 p.m.
Created at: May 3, 2026, 4:17 p.m.