Triple
T19333268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Tabasaran |
E483551
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Tabasaran language |
C41944
|
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 Tabasaran language Context triple: [Southern Tabasaran, instanceOf, variety of Tabasaran language]
-
A.
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.
-
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 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.
-
D.
Sabaic language variety
A Sabaic language variety is a specific form or dialect of the ancient South Arabian Sabaic language, distinguished by its unique linguistic features, geographic distribution, and historical context within the Sabaean cultural sphere.
-
E.
variety of the Tigre language
A variety of the Tigre language is a regional or social form of Tigre distinguished by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:33 p.m.