Triple

T23149216
Position Surface form Disambiguated ID Type / Status
Subject Ewondo language E578275 entity
Predicate hasAlternativeName P39 FINISHED
Object Kolo E393742 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: Kolo | Statement: [Ewondo language, hasAlternativeName, Kolo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kolo
Context triple: [Ewondo language, hasAlternativeName, Kolo]
  • A. Kolo chosen
    Kolo is an alternative name for the Ewondo language, a Bantu language spoken primarily in Cameroon.
  • B. Kolo
    Kolo is the given name of Kolo Touré, a retired Ivorian professional footballer known for his successful career as a defender in the English Premier League and with the Ivory Coast national team.
  • C. Kolo
    Kolo is a town in Ogbia Local Government Area of Bayelsa State in Nigeria, known as one of the communities in the Niger Delta region.
  • D. Kruhlaye
    Kruhlaye is a small town in eastern Belarus, located within the Mogilev Region.
  • E. Koliada
    Koliada is a traditional Slavic winter festival and ritual celebration associated with the winter solstice and later with Christmas, featuring caroling, feasting, and symbolic renewal.
  • 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_69e245fb8de081908f0eba7b5fd75bc4 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18ed0b76c8190ac61b949d88e9970 completed April 29, 2026, 4:53 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0c30963b3c8190a4ffb48b03fbf77a completed May 19, 2026, 9:42 a.m.
Created at: April 17, 2026, 4:01 p.m.