Triple
T5422617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medieval Albanian |
E121287
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | stage of the Albanian language |
C1722
|
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: stage of the Albanian language Context triple: [Medieval Albanian, instanceOf, stage of the Albanian language]
-
A.
variety of the Albanian language
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.
historical language stage
chosen
A historical language stage is a distinct, temporally bounded phase in the development of a language, characterized by relatively stable structural features and documented through historical evidence.
-
C.
Anatolian language
An Anatolian language is any member of an extinct branch of the Indo-European language family once spoken in ancient Anatolia (modern-day Turkey), including languages such as Hittite, Luwian, and Lycian.
-
D.
Alpine language
Alpine language is a conceptual class representing any linguistic system that has evolved within or is predominantly used in mountainous Alpine regions, shaped by their geography, culture, and historical isolation.
-
E.
Berber language grouping
A Berber language grouping is a conceptual class that encompasses the related Afroasiatic languages spoken by Berber (Amazigh) peoples across North Africa, classified together based on shared historical, structural, 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_69bd463b58d88190b258261573de9e91 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:06 p.m.