Triple
T8674809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bajelani dialect |
E205887
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Gorani language |
C24846
|
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 Gorani language Context triple: [Bajelani dialect, instanceOf, variety of Gorani language]
-
A.
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.
-
B.
variety of Tajik language
A variety of Tajik language is a regional or social form of Tajik distinguished by specific phonological, lexical, and grammatical features while remaining mutually intelligible with other forms of Tajik.
-
C.
variety of the Albanian language
A variety of the Albanian language is a distinct, systematically patterned form of Albanian—such as a dialect, sociolect, or regional speech form—characterized by unique phonological, lexical, and grammatical features within the broader Albanian linguistic continuum.
-
D.
Gondi language variety
A Gondi language variety is a specific regional or social form of the Gondi language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader Dravidian language continuum.
-
E.
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.
- 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_69ca83529a9c8190b5c075b4f14636ed |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:31 p.m.