Triple
T6056962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altsächsisch |
E134937
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | altgermanische Sprache |
C243
|
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: altgermanische Sprache Context triple: [Altsächsisch, instanceOf, altgermanische Sprache]
-
A.
Upper German dialects
Upper German dialects are a group of High German dialects spoken primarily in southern Germany, Austria, Switzerland, Liechtenstein, and parts of northern Italy and Alsace, characterized by extensive consonant shifts and distinct phonological and lexical features from other German varieties.
-
B.
West Germanic language
chosen
A West Germanic language is a member of the Germanic branch of the Indo-European language family that evolved in western and central Europe, including languages such as English, German, and Dutch.
-
C.
medieval North Germanic language variety
A medieval North Germanic language variety is a historical form of a Scandinavian language spoken in Northern Europe during the Middle Ages, characterized by its distinct phonology, morphology, and vocabulary relative to both earlier Norse and later modern Scandinavian languages.
-
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.
form of German
A form of German is a specific variety or manifestation of the German language, such as a dialect, standard register, historical stage, or regional sociolect.
- 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_69c00877b6d4819096b0e163728b73a3 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:09 p.m.