Triple

T23149217
Position Surface form Disambiguated ID Type / Status
Subject Ewondo language E578275 entity
Predicate hasAlternativeName P39 FINISHED
Object Yaunde E1201571 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: Yaunde | Statement: [Ewondo language, hasAlternativeName, Yaunde]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yaunde
Context triple: [Ewondo language, hasAlternativeName, Yaunde]
  • A. Yaunde chosen
    Yaunde is an alternative name for Kolo, likely referring to the same place or entity under a different local or historical designation.
  • B. Mogoro
    Mogoro is a small town and municipality in central-western Sardinia, Italy, known for its traditional crafts and wine production.
  • C. Limuru
    Limuru is a highland town in central Kenya known for its cool climate, tea plantations, and proximity to Nairobi.
  • D. Oshakati
    Oshakati is a major northern Namibian town that serves as an important commercial and administrative hub.
  • E. Mbewuleni
    Mbewuleni is a rural village in South Africa’s Eastern Cape province, best known as the birthplace of former South African president Thabo Mbeki.
  • 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.