Triple
T23468915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ewi of Ado-Ekiti |
E569171
|
entity |
| Predicate | titleStyle |
P2097
|
FINISHED |
| Object | Oba |
—
|
NE NERFINISHED |
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: Oba | Statement: [Ewi of Ado-Ekiti, titleStyle, Oba]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oba Context triple: [Ewi of Ado-Ekiti, titleStyle, Oba]
-
A.
Oba
Oba is a Yoruba river orisha revered as one of the wives of the thunder god Shango, associated with marital fidelity, sacrifice, and emotional resilience.
-
B.
Oba
chosen
Oba is a traditional Yoruba royal title used for kings and paramount rulers in parts of Nigeria and neighboring regions.
-
C.
Osanobua
Osanobua is the supreme creator god and central deity in the traditional religion and cosmology of the Edo people of Nigeria.
-
D.
Obu
Obu is a city in Aichi Prefecture, Japan, known as part of the industrial region surrounding Nagoya.
-
E.
Osubi
Osubi is a town in Delta State, Nigeria, known for hosting a regional airport that serves the nearby city of Warri and surrounding communities.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a6feb5688190ad4ce42fc9590adb |
completed | April 29, 2026, 6:36 a.m. |
Created at: April 17, 2026, 5:54 p.m.