Triple
T15266389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lagos Mainland |
E364910
|
entity |
| Predicate | hasNeighbourhood |
P4813
|
FINISHED |
| Object | Ojota |
E982048
|
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: Ojota | Statement: [Lagos Mainland, hasNeighbourhood, Ojota]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ojota Context triple: [Lagos Mainland, hasNeighbourhood, Ojota]
-
A.
Ojota
chosen
Ojota is a busy Lagos suburb and transport hub known for its major bus terminal and strategic location along key routes in the city.
-
B.
Oloibiri
Oloibiri is a historic town in Bayelsa State, Nigeria, best known as the site where commercial quantities of crude oil were first discovered in the country.
-
C.
Ojowo
Ojowo is a town within the Ijebu North area of Ogun State in southwestern Nigeria.
-
D.
Odogbolu
Odogbolu is a town and local government area in Ogun State, southwestern Nigeria, historically under the traditional authority of the Awujale of Ijebu.
-
E.
Jirapa
Jirapa is a town in Ghana that serves as a local administrative and commercial center in the country’s Upper West Region.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00851c5b88190a296b6a105d3ee30 |
completed | April 15, 2026, 9:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fee600340c8190a1888d35c2c1bc86 |
completed | May 9, 2026, 7:45 a.m. |
Created at: April 10, 2026, 3:14 a.m.