Triple
T36662398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinyar of Sudan |
E905165
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Sinyar language |
C64141
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: variety of Sinyar language Context triple: [Sinyar of Sudan, instanceOf, variety of Sinyar language]
-
A.
variety of Saisiyat language
A variety of the Saisiyat language is a distinct regional or social form of Saisiyat characterized by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other forms.
-
B.
variety of the Isinay language
A variety of the Isinay language is a regional or social form of Isinay distinguished by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other forms.
-
C.
variety of Siwu language
A variety of the Siwu language is a distinct regional or social form of Siwu characterized by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other forms.
-
D.
variety of Shina language
A variety of the Shina language is a regional or social dialect of Shina distinguished by its unique phonological, lexical, or grammatical features while remaining mutually intelligible to varying degrees with other Shina dialects.
-
E.
variety of the Sui language
A variety of the Sui language is a distinct regional or social form of Sui characterized by systematic differences in pronunciation, vocabulary, and grammar while remaining mutually intelligible with other Sui forms.
- F. None of above. chosen
Provenance (1 batch)
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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.