Triple

T2534275
Position Surface form Disambiguated ID Type / Status
Subject Oya E56231 entity
Predicate spouse P13 FINISHED
Object Ogun E57806 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: Ogun | Statement: [Oya, spouse, Ogun]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ogun
Context triple: [Oya, spouse, Ogun]
  • A. Ogun chosen
    Ogun is a major Yoruba deity revered as the god of iron, war, and craftsmanship, often associated with metalworking, technology, and the clearing of paths.
  • B. Shango
    Shango is a major Yoruba orisha revered as the powerful god of thunder, lightning, and justice, often associated with kingship and drumming.
  • C. Ifa
    Ifa is a Yoruba divination and spiritual system centered on a complex corpus of sacred texts and the guidance of the deity Orunmila.
  • D. Olodumare
    Olodumare is the supreme creator deity and ultimate source of power and existence in Yoruba religion and cosmology.
  • E. Odinani
    Odinani is the indigenous spiritual and cosmological belief system of the Igbo people of southeastern Nigeria, encompassing their deities, rituals, moral codes, and worldview.
  • 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_69ab4a49b6508190bc467fbef4bac334 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abd27c8650819080005869789b802c completed March 7, 2026, 7:23 a.m.
NED1 Entity disambiguation (via context triple) batch_69af2bbc416c81908774782420b54664 completed March 9, 2026, 8:21 p.m.
Created at: March 6, 2026, 9:47 p.m.