Triple

T30952516
Position Surface form Disambiguated ID Type / Status
Subject Cakfem-Mushere language E788583 entity
Predicate spokenBy P2181 FINISHED
Object Mushere people
The Mushere people are an ethnic group, likely based in Nigeria’s Plateau region, known for their distinct cultural traditions and use of the Cakfem-Mushere language.
E2291619 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: Mushere people | Statement: [Cakfem-Mushere language, spokenBy, Mushere people]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Mushere people
Triple: [Cakfem-Mushere language, spokenBy, Mushere people]
Generated description
The Mushere people are an ethnic group, likely based in Nigeria’s Plateau region, known for their distinct cultural traditions and use of the Cakfem-Mushere language.

Provenance (5 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_69f224c28c1881908c33b45d689f1724 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f693460b6c81908a0aa7c2b72699ec completed May 3, 2026, 12:13 a.m.
NED1 Entity disambiguation (via context triple) batch_6a5c75366c948190a4f7ea9a20a9bcbf completed July 19, 2026, 6:56 a.m.
NEDg Description generation batch_6a5c7607ac748190ab2a99597c5f93af completed July 19, 2026, 7 a.m.
NED2 Entity disambiguation (via description) batch_6a5c762bedcc819083412757166eaa34 completed July 19, 2026, 7:01 a.m.
Created at: April 29, 2026, 8:53 p.m.