Triple

T26605823
Position Surface form Disambiguated ID Type / Status
Subject Kinyamwezi E667767 entity
Predicate hasDialects P4251 FINISHED
Object Southern Kinyamwezi
Southern Kinyamwezi is a regional variety of the Kinyamwezi Bantu language spoken by communities in the southern part of the Nyamwezi-speaking area of Tanzania.
E1742335 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: Southern Kinyamwezi | Statement: [Kinyamwezi, hasDialects, Southern Kinyamwezi]
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: Southern Kinyamwezi
Triple: [Kinyamwezi, hasDialects, Southern Kinyamwezi]
Generated description
Southern Kinyamwezi is a regional variety of the Kinyamwezi Bantu language spoken by communities in the southern part of the Nyamwezi-speaking area of Tanzania.

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_69ee9cfd20348190bb1255d2603efb7a completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f615734f888190b144b23c68324b7e completed May 2, 2026, 3:17 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12092900e48190ababef4790a4f91b completed May 23, 2026, 8:08 p.m.
NEDg Description generation batch_6a120ab522c481909ca39611bcc945ed completed May 23, 2026, 8:14 p.m.
NED2 Entity disambiguation (via description) batch_6a120b39cddc8190a6c89274fc238b1a completed May 23, 2026, 8:16 p.m.
Created at: April 27, 2026, 2:14 a.m.