Triple

T12712205
Position Surface form Disambiguated ID Type / Status
Subject Ado-Odo/Ota E303746 entity
Predicate hasMajorTown P316 FINISHED
Object Oju-Ore E996878 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: Oju-Ore | Statement: [Ado-Odo/Ota, hasMajorTown, Oju-Ore]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oju-Ore
Context triple: [Ado-Odo/Ota, hasMajorTown, Oju-Ore]
  • A. Ogboru
    Ogboru is a traditional deity revered by the Urhobo people of Nigeria, associated with their indigenous religious beliefs and cultural practices.
  • B. Osogbo
    Osogbo is a major city in southwestern Nigeria known for its rich Yoruba cultural heritage and the UNESCO-listed Osun-Osogbo Sacred Grove.
  • 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. Eze Ogo
    Eze Ogo is a traditional leadership title in Ohafia, a prominent Igbo community in southeastern Nigeria, associated with local authority and cultural stewardship.
  • E. Oke-Ore chosen
    Oke-Ore is a notable town within the Ado-Odo/Ota local government area of Ogun State in southwestern Nigeria.
  • 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_69d7bdf084148190ab9d513dc0735af4 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96208fa6481909d6fd43654752a2d completed April 10, 2026, 8:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6f5b9e0c4819095194dc42677e17f completed May 3, 2026, 7:14 a.m.
Created at: April 9, 2026, 5:23 p.m.