Triple
T21972702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arvanitika of Attica |
E542629
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Balkan Gheg 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 Gheg variety Context triple: [Arvanitika of Attica, instanceOf, Balkan Gheg variety]
-
A.
Balkan Slavic dialects
Balkan Slavic dialects are a group of South Slavic vernaculars spoken in the Balkan Peninsula that share distinctive grammatical and phonological features shaped by intense contact with neighboring Balkan languages.
-
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.
para-Romani variety
A para-Romani variety is a mixed language in which Romani-derived vocabulary is embedded into the grammatical structure of a surrounding majority language, typically used as an in-group code by Romani or Romani-associated communities.
-
D.
Balkan language
A Balkan language is any language spoken in the Balkan Peninsula that often shares grammatical and lexical features with neighboring tongues due to long-term contact and convergence.
-
E.
Eastern South Slavic dialect group
The Eastern South Slavic dialect group comprises the continuum of closely related Slavic dialects spoken primarily in Bulgaria and North Macedonia, forming the basis of the Bulgarian and Macedonian standard languages.
- 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_69e0c48070988190909db97667b9a0ac |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 8:02 p.m.