Triple

T13558616
Position Surface form Disambiguated ID Type / Status
Subject Akoko E323843 entity
Predicate hasMajorSettlement P316 FINISHED
Object Epinmi-Akoko E328601 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: Epinmi-Akoko | Statement: [Akoko, hasMajorSettlement, Epinmi-Akoko]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Epinmi-Akoko
Context triple: [Akoko, hasMajorSettlement, Epinmi-Akoko]
  • A. Odukpani
    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. Issele-Azagba
    Issele-Azagba is a town in Aniocha South Local Government Area of Delta State in southern Nigeria.
  • C. Ikorodu
    Ikorodu is a rapidly growing suburban city and local government area in the northeastern part of Lagos State, Nigeria, known for its residential communities and emerging commercial activity.
  • D. Ikare-Akoko chosen
    Ikare-Akoko is a major commercial and cultural town in southwestern Nigeria, serving as one of the key urban centers in the Akoko region.
  • E. Gbekon
    Gbekon is a regional dialect of the Fon language spoken by Fon communities in parts of West Africa, particularly in Benin.
  • 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_69d8076830b48190910a902bae5888e2 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaff4223c8190801d153ae8f94c73 completed April 12, 2026, 2:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69f75dab4974819097880ad4d50f1b34 completed May 3, 2026, 2:37 p.m.
Created at: April 9, 2026, 9:47 p.m.