Triple
T16184536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunza dialect |
E392765
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Burushaski |
C37098
|
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 Burushaski Context triple: [Hunza dialect, instanceOf, variety of Burushaski]
-
A.
Nuristani language
A Nuristani language is any member of a small group of Indo-Iranian languages spoken primarily in the remote Nuristan region of eastern Afghanistan and adjacent areas of Pakistan.
-
B.
Dardic language
A Dardic language is a member of a subgroup of the Indo-Aryan languages spoken primarily in the mountainous regions of northern Pakistan, northwestern India, and eastern Afghanistan, characterized by distinct phonological and lexical features.
-
C.
variety of Tat language
A variety of Tat language is a distinct regional or social form of the Tat language characterized by unique phonological, lexical, and grammatical features within the broader Tat-speaking community.
-
D.
variety of Ossetian language
A variety of Ossetian language is a distinct regional or social form of Ossetian characterized by specific phonological, lexical, and grammatical features within the broader Ossetian linguistic continuum.
-
E.
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.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5:02 a.m.