Triple
T22150585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sadz dialect |
E547401
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Abkhaz language |
C45862
|
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 Abkhaz language Context triple: [Sadz dialect, instanceOf, variety of Abkhaz language]
-
A.
variety of Lezgian language
A variety of the Lezgian language is a regional or social form of Lezgian distinguished by systematic differences in pronunciation, vocabulary, and sometimes grammar while remaining mutually intelligible with other forms.
-
B.
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.
-
C.
variety of Avar language
A variety of Avar language is a regional or social form of the Avar language distinguished by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Avar forms.
-
D.
variety of Belarusian language
A variety of the Belarusian language is a regionally or socially distinct form of Belarusian characterized by specific phonological, lexical, and grammatical features within the broader Belarusian linguistic system.
-
E.
variety of Tabasaran language
A variety of the Tabasaran language is a regional or social form of Tabasaran distinguished by systematic differences in pronunciation, vocabulary, or grammar within the broader Tabasaran linguistic continuum.
- 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:33 p.m.