Triple

T13558619
Position Surface form Disambiguated ID Type / Status
Subject Akoko E323843 entity
Predicate hasMajorSettlement P316 FINISHED
Object Afin-Akoko E1052788 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: Afin-Akoko | Statement: [Akoko, hasMajorSettlement, Afin-Akoko]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Afin-Akoko
Context triple: [Akoko, hasMajorSettlement, Afin-Akoko]
  • A. Akoko
    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. Isua-Akoko chosen
    Isua-Akoko is a prominent town in the Akoko area of Ondo State, southwestern Nigeria.
  • C. Akuku
    Akuku is a settlement located within the Akoko-Edo area of Edo State in southern Nigeria.
  • D. Akwamu
    Akwamu was a powerful early modern West African kingdom of the Akan people, known for its military expansion and control of key trade routes in what is now Ghana.
  • E. Tagakaolo
    Tagakaolo is an indigenous ethnolinguistic group in the southern Philippines, primarily in parts of Davao and Sarangani, known for its distinct Austronesian language and cultural traditions.
  • 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_69f794281fb48190882f164df1def07e completed May 3, 2026, 6:30 p.m.
Created at: April 9, 2026, 9:47 p.m.