Triple
T12835349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akpabuyo |
E306895
|
entity |
| Predicate | sharesBorderWith |
P224
|
FINISHED |
| Object | Odukpani |
E306891
|
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: Odukpani | Statement: [Akpabuyo, sharesBorderWith, Odukpani]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Odukpani Context triple: [Akpabuyo, sharesBorderWith, Odukpani]
-
A.
Odukpani
chosen
Odukpani is a local government area in southeastern Nigeria known for its diverse ethnic communities and proximity to the state capital, Calabar, in Cross River State.
-
B.
Obuasi
Obuasi is a major Ghanaian mining town renowned for its large gold deposits and historic gold mine.
-
C.
Nkwanta
Nkwanta is a town in northeastern Ghana that serves as an important local commercial and administrative center within the Oti Region.
-
D.
Dangme
Dangme is a Kwa language spoken primarily by the Dangme people in southeastern Ghana.
-
E.
Abura-Dunkwa
Abura-Dunkwa is a town in Ghana that serves as the capital of the Abura-Asebu-Kwamankese District in the Central 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96fb1c7248190bb6e644e041d192e |
completed | April 10, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f69b9bb0b48190ba3f9f92d270db83 |
completed | May 3, 2026, 12:49 a.m. |
Created at: April 9, 2026, 5:34 p.m.