Triple
T5386378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geg |
E120209
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Albanian |
C5233
|
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 Albanian Context triple: [Geg, instanceOf, variety of Albanian]
-
A.
variety of the Albanian language
chosen
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.
-
B.
variety of the Greek language
A variety of the Greek language is a distinct form or dialect of Greek, characterized by specific phonological, grammatical, lexical, and pragmatic features used by a particular community or in a particular context.
-
C.
variety of Turkish
A variety of Turkish is a distinct form or dialect of the Turkish language characterized by unique phonological, lexical, and grammatical features associated with a particular region, community, or social group.
-
D.
variety of Arabic
A variety of Arabic is a distinct form of the Arabic language, characterized by its own phonological, lexical, and grammatical features, typically associated with a particular region, community, or social context.
-
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.
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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
Created at: March 20, 2026, 2:03 p.m.