Triple

T6771518
Position Surface form Disambiguated ID Type / Status
Subject Nawuri language E155053 entity
Predicate closelyRelatedTo P37 FINISHED
Object Gonja language E267649 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: Gonja language | Statement: [Nawuri language, closelyRelatedTo, Gonja language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gonja language
Context triple: [Nawuri language, closelyRelatedTo, 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. Sanglechi language
    The Sanglechi language is an Eastern Iranian language spoken by a small community in the Sanglech Valley region of Afghanistan and Tajikistan.
  • D. Dagbani language
    Dagbani is a major Gur language of northern Ghana, spoken primarily by the Dagomba people and used widely in education, media, and regional communication.
  • E. Guna language
    Guna language is an indigenous Chibchan language spoken by the Guna people of Panama and Colombia.
  • 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_69c68812ef7c819099369f51febb725c completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d2496fa08190895d8b625fb0d699 completed March 27, 2026, 6:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69c712c75b9c819099b0be616925a0b9 completed March 27, 2026, 11:29 p.m.
Created at: March 27, 2026, 2:13 p.m.