Triple
T13048926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akure people |
E327396
|
entity |
| Predicate | usesTraditionalTitle |
P103879
|
FINISHED |
| Object | Iyalode |
E1032960
|
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: Iyalode | Statement: [Akure people, usesTraditionalTitle, Iyalode]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Iyalode Context triple: [Akure people, usesTraditionalTitle, Iyalode]
-
A.
Oluremi
Oluremi is a feminine given name of Yoruba origin, commonly used in Nigeria and among Yoruba-speaking communities.
-
B.
Oluyemi
Oluyemi is a Yoruba given name, notably borne by Nigerian politician and former Vice President Yemi Osinbajo.
-
C.
Omoloko
Omoloko is an Afro-Brazilian religious tradition that blends Yoruba-derived orixá worship with elements of other African, Indigenous, and Catholic spiritual practices.
-
D.
Oloye
chosen
Oloye is a traditional Yoruba chieftaincy title signifying a person of high social and cultural status within the community.
-
E.
Odogbolu
Odogbolu is a town and local government area in Ogun State, southwestern Nigeria, historically under the traditional authority of the Awujale of Ijebu.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98bce3678819082a7aa1d83f20592 |
completed | April 10, 2026, 11:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f76b98a7c48190a2ca0ec7b9bd8d19 |
completed | May 3, 2026, 3:36 p.m. |
Created at: April 9, 2026, 8:57 p.m.