Triple
T12099492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eti-Osa |
E288153
|
entity |
| Predicate | containsArea |
P11790
|
FINISHED |
| Object | Ikoyi |
E327246
|
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: Ikoyi | Statement: [Eti-Osa, containsArea, Ikoyi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ikoyi Context triple: [Eti-Osa, containsArea, Ikoyi]
-
A.
Ikoyi
chosen
Ikoyi is an affluent, high-end residential and commercial district in Lagos, Nigeria, known for its luxury real estate, upscale hotels, and diplomatic presence.
-
B.
Ibeju-Lekki
Ibeju-Lekki is a rapidly developing local government area in Lagos State, Nigeria, known for major infrastructure projects, emerging residential estates, and proximity to the Lekki Free Trade Zone and Dangote Refinery.
-
C.
Eso Ikoyi
Eso Ikoyi were an elite warrior caste of the Oyo Empire in Yorubaland, renowned for their strict code of honor, bravery, and key role in the empire’s military campaigns.
-
D.
Lekki
Lekki is a fictional companion mascot character associated with Nokki, likely designed as a cute, supportive sidekick figure.
-
E.
Lekki
Lekki is the official mascot character created for the XVIII Olympic Winter Games.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9155465388190bbe52453c9b11912 |
completed | April 10, 2026, 3:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f63ee0597c81909ad679a1ddece887 |
completed | May 2, 2026, 6:13 p.m. |
Created at: April 8, 2026, 9:48 p.m.