Triple
T5709453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arvanitika |
E125867
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Balkan language variety |
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: Balkan language variety Context triple: [Arvanitika, instanceOf, Balkan language variety]
-
A.
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.
-
B.
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.
-
C.
Eastern Romance language
An Eastern Romance language is a member of the Romance branch of the Indo-European language family that evolved from Eastern varieties of Vulgar Latin, primarily spoken in the Balkans and surrounding regions.
-
D.
Romance language variety
A Romance language variety is a specific form or dialect of a Romance language, distinguished by its unique phonological, grammatical, and lexical features within the broader Romance language family.
-
E.
West Slavic languages
West Slavic languages are a subgroup of the Slavic language family, including Polish, Czech, Slovak, and related languages, primarily spoken in Central Europe and characterized by shared phonological, grammatical, and lexical features.
- 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_69c0082d6fe48190b777fb383769e5c8 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:46 p.m.