Triple

T12969158
Position Surface form Disambiguated ID Type / Status
Subject Volta–Niger languages E321347 entity
Predicate containsLanguage P2177 FINISHED
Object Akoko E323843 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: Akoko | Statement: [Volta–Niger languages, containsLanguage, Akoko]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Akoko
Context triple: [Volta–Niger languages, containsLanguage, Akoko]
  • A. Akoko chosen
    Akoko is a prominent Yoruba sub-ethnic group in southwestern Nigeria, primarily inhabiting the northeastern part of Ondo State and parts of neighboring states.
  • B. Akoka
    Akoka is a neighborhood in Lagos, Nigeria, known for hosting parts of the University of Lagos and being situated within the Yaba area.
  • C. Oloko
    Oloko is a town in Ikwuano Local Government Area of Abia State in southeastern Nigeria, known for its predominantly Igbo population and agrarian community.
  • D. Akuku
    Akuku is a settlement located within the Akoko-Edo area of Edo State in southern Nigeria.
  • E. Ake
    Ake is a district in Abeokuta, Nigeria, historically known as a traditional center of Egba leadership and culture.
  • 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_69d80763bd6c819094437da5b20b01d2 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d97e407e5081909424fc0c22483c28 completed April 10, 2026, 10:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6b8e6b31c8190b09276003f284f25 completed May 3, 2026, 2:54 a.m.
Created at: April 9, 2026, 8:33 p.m.