Triple
T15268887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Bavarian |
E364969
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bavarian dialect |
C17197
|
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: Bavarian dialect Context triple: [Southern Bavarian, instanceOf, Bavarian dialect]
-
A.
Upper German dialects
chosen
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.
Low German dialect
A Low German dialect is a regional variety of the West Germanic language continuum spoken mainly in northern Germany and parts of the eastern Netherlands, characterized by distinct phonological, lexical, and grammatical features that differentiate it from High German.
-
C.
Central German dialect
A Central German dialect is a variety of the German language spoken in the central regions of Germany, characterized by linguistic features that are intermediate between Upper and Low German dialects.
-
D.
Sudeten German
A Sudeten German was an ethnic German inhabitant of the Sudetenland regions of Bohemia, Moravia, and Czech Silesia, historically within Czechoslovakia, particularly noted for their role in the political tensions leading up to World War II.
-
E.
Austrian
An Austrian is a person or attribute related to Austria, encompassing its nationality, culture, language, or origin.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:14 a.m.