Triple
T12166009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arugba |
E289834
|
entity |
| Predicate | location |
P40
|
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: [Arugba, location, Osogbo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Osogbo Context triple: [Arugba, location, 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.
Ikwere
Ikwere is an ethnic group and language community primarily located in Rivers State in the Niger Delta region of Nigeria.
-
D.
Elegbá
Elegbá is a powerful Yoruba and Afro-Caribbean orisha known as the divine messenger and guardian of crossroads, communication, and destiny.
-
E.
Ayegunle
Ayegunle is a village in southwestern Nigeria known as one of the communities where the Ukaan language is traditionally spoken.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e4deb308190aa1a99a78d46b461 |
completed | May 2, 2026, 3:54 p.m. |
Created at: April 8, 2026, 9:50 p.m.