Triple
T28533919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crimean Gothic |
E722110
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Gothic dialect |
C54215
|
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: Gothic dialect Context triple: [Crimean Gothic, instanceOf, Gothic dialect]
-
A.
Gothic-language text
A Gothic-language text is any written work composed in the extinct East Germanic language Gothic, typically preserved in manuscripts such as biblical translations and legal or liturgical documents from the early medieval period.
-
B.
Norman dialect
Norman dialect is a variety of the Romance language Norman, historically spoken in the region of Normandy and its surrounding areas, characterized by distinct phonological, lexical, and grammatical features that differentiate it from standard French.
-
C.
Scandinavian dialect
A Scandinavian dialect is a regional or social variety of a North Germanic language (such as Swedish, Danish, or Norwegian) characterized by distinct pronunciation, vocabulary, and grammar within the Scandinavian region.
-
D.
Gutnish variety
A Gutnish variety is a regional form of the Gutnish language spoken on the island of Gotland and surrounding areas, characterized by distinct phonological, lexical, and grammatical features that differentiate it from standard Swedish and other Scandinavian dialects.
-
E.
Goral dialect
Goral dialect is a group of closely related Slavic vernaculars spoken by the Goral people in the mountainous regions along the Polish-Slovak border, characterized by features of Polish, Slovak, and other neighboring languages.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:30 a.m.