Triple

T13558609
Position Surface form Disambiguated ID Type / Status
Subject Akoko E323843 entity
Predicate hasMajorSettlement P316 FINISHED
Object Oka-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: Oka-Akoko | Statement: [Akoko, hasMajorSettlement, Oka-Akoko]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oka-Akoko
Context triple: [Akoko, hasMajorSettlement, Oka-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. Ōtoku
    Ōtoku was a Japanese era name (nengō) of the late 11th century, used during the reign of Emperor Shirakawa.
  • C. Akawaio
    The Akawaio are an Indigenous people of the Guiana Highlands in Guyana, Venezuela, and Brazil, known for their Cariban language and traditional forest-based way of life.
  • D. Ohoka
    Ohoka is a small rural township in New Zealand’s Canterbury region, known for its lifestyle properties and proximity to Christchurch.
  • E. Asokoro
    Asokoro is an upscale residential and administrative district in Abuja, Nigeria, known for hosting many government institutions, embassies, and high-profile residents.
  • 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.