Triple

T33830403
Position Surface form Disambiguated ID Type / Status
Subject Maban-speaking peoples E867081 entity
Predicate hasEthnicGroup P1898 FINISHED
Object Surbakhal people
The Surbakhal people are an ethnic group belonging to the Maban-speaking communities of the border regions of Chad and Sudan in Central Africa.
E2070333 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: Surbakhal people | Statement: [Maban-speaking peoples, hasEthnicGroup, Surbakhal 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: Surbakhal people
Triple: [Maban-speaking peoples, hasEthnicGroup, Surbakhal people]
Generated description
The Surbakhal people are an ethnic group belonging to the Maban-speaking communities of the border regions of Chad and Sudan in Central Africa.

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_69f34991dd248190a659541588506b3c completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f70022ccc88190abdc55e89e3d3172 completed May 3, 2026, 7:58 a.m.
NED1 Entity disambiguation (via context triple) batch_6a366ea6d0e08190ae46c6202d4129a0 completed June 20, 2026, 10:42 a.m.
NEDg Description generation batch_6a366f45cc34819085bc33795237af77 completed June 20, 2026, 10:45 a.m.
NED2 Entity disambiguation (via description) batch_6a36710b582c8190a9510e1ab6c5d1e0 completed June 20, 2026, 10:52 a.m.
Created at: May 1, 2026, 1:46 a.m.