Triple
T16958540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ijo–Defaka |
E411366
|
entity |
| Predicate | hasNotableLanguage |
P7390
|
FINISHED |
| Object | Okrika Ijo |
E397382
|
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: Okrika Ijo | Statement: [Ijo–Defaka, hasNotableLanguage, Okrika Ijo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Okrika Ijo Context triple: [Ijo–Defaka, hasNotableLanguage, Okrika Ijo]
-
A.
Oke-Ore
Oke-Ore is a notable town within the Ado-Odo/Ota local government area of Ogun State in southwestern Nigeria.
-
B.
Okeke
Okeke is a common Igbo surname of Nigerian origin, borne by many individuals across various professions and regions.
-
C.
Okorie
Okorie is a Nigerian surname, notably borne by the reggae-dancehall singer Patoranking.
-
D.
Okrika Ijaw
chosen
Okrika Ijaw are a prominent coastal subgroup of the Ijaw ethnic group in Nigeria, traditionally known for fishing, trade, and their role in the Niger Delta region.
-
E.
Igan Okoto
Igan Okoto is a prominent town in Yewa North Local Government Area of Ogun State, 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d01e420881909be1d93d7d6772fd |
completed | April 18, 2026, 6:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00d468f5048190aa43b212ec7a7306 |
completed | May 10, 2026, 6:54 p.m. |
Created at: April 10, 2026, 5:31 a.m.