Triple

T30516009
Position Surface form Disambiguated ID Type / Status
Subject Shabaki E776566 entity
Predicate hasAlternativeName P39 FINISHED
Object Shabak language
Shabak language is an Indo-Iranian language spoken primarily by the Shabak people in northern Iraq, notable for its blend of Kurdish, Arabic, and Persian influences.
E1920127 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: Shabak language | Statement: [Shabaki, hasAlternativeName, Shabak language]
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: Shabak language
Triple: [Shabaki, hasAlternativeName, Shabak language]
Generated description
Shabak language is an Indo-Iranian language spoken primarily by the Shabak people in northern Iraq, notable for its blend of Kurdish, Arabic, and Persian influences.

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_69f2249b23c4819087fa85496d92f43f completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f68805b4848190b75da14996d52a38 completed May 2, 2026, 11:25 p.m.
NED1 Entity disambiguation (via context triple) batch_6a27be6fbe1c8190b442e3add776ddff completed June 9, 2026, 7:19 a.m.
NEDg Description generation batch_6a27c8dbfc2c81908f73369e5bad4aca completed June 9, 2026, 8:03 a.m.
NED2 Entity disambiguation (via description) batch_6a27c96995e08190b27a0c8e400e6804 completed June 9, 2026, 8:06 a.m.
Created at: April 29, 2026, 8:16 p.m.