Triple

T23160491
Position Surface form Disambiguated ID Type / Status
Subject Gonja E578567 entity
Predicate language P15 FINISHED
Object Gonja language NE NERFINISHED

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: Gonja language | Statement: [Gonja, language, Gonja language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gonja language
Context triple: [Gonja, language, Gonja language]
  • A. Gonja language chosen
    The Gonja language is a Gur language spoken primarily by the Gonja people in northern Ghana.
  • B. Ghanongga language
    The Ghanongga language is an Oceanic language spoken by indigenous communities on New Georgia Island in the Solomon Islands.
  • C. Gola language
    Gola language is a Niger–Congo language spoken by the Gola people of Liberia and neighboring regions of West Africa.
  • D. Ganguela language
    The Ganguela language is a Bantu language spoken by the Ganguela people of southwestern Africa, particularly in Angola.
  • E. Ganza language
    Ganza language is a lesser-known Afroasiatic language spoken by communities in southwestern Ethiopia and neighboring regions.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e245fc75348190a0288401044c8af8 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18f006930819097aafef87405d737 completed April 29, 2026, 4:54 a.m.
Created at: April 17, 2026, 4:02 p.m.