Triple
T15626854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purgi language |
E375699
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Western Himalayan language |
C33096
|
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: Western Himalayan language Context triple: [Purgi language, instanceOf, Western Himalayan language]
-
A.
Dardic language
chosen
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.
-
B.
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.
-
C.
Bihari languages
Bihari languages are a group of closely related Indo-Aryan languages and dialects spoken primarily in the Indian state of Bihar and surrounding regions, including Bhojpuri, Maithili, and Magahi.
-
D.
Sino-Tibetan language
A Sino-Tibetan language is any member of a large language family, including Chinese and Tibeto-Burman languages, characterized by shared historical origins in East and Southeast Asia and often featuring tonal systems and analytic grammar.
-
E.
Cordilleran language
A Cordilleran language is a member of a proposed subgroup of the Austronesian language family spoken in the Cordillera mountain region of northern Luzon in the Philippines, characterized by shared phonological, lexical, and grammatical features distinct from neighboring language groups.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:14 a.m.