Triple

T22720363
Position Surface form Disambiguated ID Type / Status
Subject Guan peoples E561841 entity
Predicate subgroup P10 FINISHED
Object Gonja 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 | Statement: [Guan peoples, subgroup, Gonja]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gonja
Context triple: [Guan peoples, subgroup, Gonja]
  • A. Gonja chosen
    Gonja are an ethnic group in northern Ghana known for their distinct language, chieftaincy traditions, and historical Gonja kingdom.
  • B. Gashua
    Gashua is a town in northeastern Nigeria that serves as an important commercial and administrative center in Yobe State.
  • C. Negombo
    Negombo is a coastal city in western Sri Lanka known historically as a strategic colonial port and today for its fishing industry and beach tourism.
  • D. Banjima
    Banjima is an Aboriginal Australian people traditionally associated with the Pilbara region of Western Australia, known for their distinct language and cultural heritage.
  • E. Dungu
    Dungu is a town in northeastern Democratic Republic of the Congo, known as a local administrative and trading center near the Garamba National Park.
  • 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_69e2454fc984819088213b58ee87a002 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f17910deb48190b38174e16868f3dd completed April 29, 2026, 3:20 a.m.
Created at: April 17, 2026, 3:19 p.m.