Triple
T17717091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thari Sindhi |
E442227
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Sindhi language |
C14883
|
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 Sindhi language Context triple: [Thari Sindhi, instanceOf, variety of Sindhi language]
-
A.
variety of Sindhi
chosen
A variety of Sindhi is a distinct form or dialect of the Sindhi language characterized by unique phonological, lexical, and grammatical features associated with a particular region, community, or social group.
-
B.
variety of Punjabi language
A variety of Punjabi language is a distinct regional or social form of Punjabi characterized by unique phonological, lexical, and sometimes grammatical features while remaining mutually intelligible with other Punjabi forms.
-
C.
variety of Urdu
A variety of Urdu is a distinct form of the Urdu language characterized by unique phonological, lexical, syntactic, and sociolinguistic features associated with a particular region, community, or context.
-
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 Gorani language
A variety of Gorani language is a regional or social form of the Gorani speech continuum, distinguished by its own phonological, lexical, and grammatical features while remaining mutually intelligible with other Gorani varieties.
- F. None of above.
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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:06 a.m.