Triple
T13803235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilorin East |
E331692
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Oke Oyi |
E1062292
|
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: Oke Oyi | Statement: [Ilorin East, hasSettlement, Oke Oyi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oke Oyi Context triple: [Ilorin East, hasSettlement, Oke Oyi]
-
A.
Oke Oyi
chosen
Oke Oyi is a town in Kwara State, Nigeria, serving as the administrative headquarters of Ilorin East Local Government Area.
-
B.
Oke Sopen
Oke Sopen is a town located within the Ijebu North area of Ogun State in southwestern Nigeria.
-
C.
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.
-
D.
Ogboru
Ogboru is a traditional deity revered by the Urhobo people of Nigeria, associated with their indigenous religious beliefs and cultural practices.
-
E.
Oke-Ore
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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de026c36108190a7436034a730a261 |
completed | April 14, 2026, 9:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b8da594c81908cb878a8cc1b3a72 |
completed | May 3, 2026, 9:06 p.m. |
Created at: April 9, 2026, 10:12 p.m.