Triple
T9045094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imeretian dialect |
E216735
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of the Georgian language |
C25509
|
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: regional variety of the Georgian language Context triple: [Imeretian dialect, instanceOf, regional variety of the Georgian language]
-
A.
Kartvelian language
A Kartvelian language is a member of a small family of indigenous languages of the South Caucasus, including Georgian, Svan, Mingrelian, and Laz, characterized by complex phonology and morphology and no proven genetic relation to other language families.
-
B.
Kartvelian language branch
The Kartvelian language branch is a small family of closely related languages indigenous to the South Caucasus, including Georgian, Svan, Mingrelian, and Laz, characterized by complex phonology and rich verb morphology.
-
C.
Kartvelian language branch
The Kartvelian language branch is a small family of closely related languages indigenous to the South Caucasus, including Georgian, Svan, Mingrelian, and Laz.
-
D.
regional variety of Azerbaijani
A regional variety of Azerbaijani is a geographically or socially localized form of the Azerbaijani language characterized by distinct phonological, lexical, and sometimes grammatical features.
-
E.
Greek language variety
A Greek language variety is a distinct form of the Greek language, characterized by specific phonological, grammatical, lexical, and pragmatic features associated with particular regions, communities, or social groups.
- 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_69ca83d22d488190adbce5e020e9cd1d |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:09 p.m.