Triple

T12640916
Position Surface form Disambiguated ID Type / Status
Subject Ataoja of Osogbo E301893 entity
Predicate jurisdiction P82 FINISHED
Object Osogbo E128015 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: Osogbo | Statement: [Ataoja of Osogbo, jurisdiction, Osogbo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Osogbo
Context triple: [Ataoja of Osogbo, jurisdiction, Osogbo]
  • A. Osogbo chosen
    Osogbo is a major city in southwestern Nigeria known for its rich Yoruba cultural heritage and the UNESCO-listed Osun-Osogbo Sacred Grove.
  • B. Ogboru
    Ogboru is a traditional deity revered by the Urhobo people of Nigeria, associated with their indigenous religious beliefs and cultural practices.
  • C. Ewu
    Ewu is a historic Esan town and traditional kingdom in Edo State, southern Nigeria, known for its cultural heritage and local monarchy.
  • D. Ikwere
    Ikwere is an ethnic group and language community primarily located in Rivers State in the Niger Delta region of Nigeria.
  • E. Elegbá
    Elegbá is a powerful Yoruba and Afro-Caribbean orisha known as the divine messenger and guardian of crossroads, communication, and destiny.
  • 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_69d7bdec9f9c8190b4bac675b7588211 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9614ae6ac8190b42acbf2b0331fda completed April 10, 2026, 8:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6eac6153c81909adff921117718d8 completed May 3, 2026, 6:27 a.m.
Created at: April 9, 2026, 5:17 p.m.