Triple

T11302901
Position Surface form Disambiguated ID Type / Status
Subject Frafra language E267639 entity
Predicate subclassOf P1244 FINISHED
Object Gurune language E917989 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: Gurune language | Statement: [Frafra language, subclassOf, Gurune language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gurune language
Context triple: [Frafra language, subclassOf, Gurune language]
  • A. Gurene language chosen
    The Gurene language is a Gur language spoken primarily by the Frafra people in northern Ghana and parts of Burkina Faso.
  • B. Gura language
    The Gura language is an Ethiopian Semitic language spoken by the Gurage people in central Ethiopia.
  • C. Gumer language
    The Gumer language is an Afroasiatic Semitic language spoken by the Gumer people of the Gurage region in central Ethiopia.
  • D. Gurma language
    Gurma language is a Gur language spoken primarily in parts of Burkina Faso, Togo, Benin, and neighboring West African countries.
  • E. Konda-Dora language
    Konda-Dora language is a Dravidian tribal language spoken primarily by the Konda Dora people in parts of Andhra Pradesh and Odisha in India.
  • 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_69d6aac993a08190a6f36445ebaf9a43 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e9a5c3788190ba54eda514b97903 completed April 9, 2026, 6:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69e525a842dc81909c84d8bd1a6414fa completed April 19, 2026, 6:57 p.m.
Created at: April 8, 2026, 9:32 p.m.