Triple
T11912317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standard German phonology |
E283425
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of Standard German |
C10722
|
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: component of Standard German Context triple: [Standard German phonology, instanceOf, component of Standard German]
-
A.
form of German
chosen
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.
-
B.
German word
A German word is a linguistic unit in the German language that carries meaning and can function independently or as part of larger expressions in speech and writing.
-
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.
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.
-
E.
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.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:44 p.m.