Triple
T36590720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giessen dialect |
E902661
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Central Hessian dialect |
C29038
|
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: Central Hessian dialect Context triple: [Giessen dialect, instanceOf, Central Hessian dialect]
-
A.
Central German dialect
chosen
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.
-
B.
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.
-
C.
Low Franconian dialects
Low Franconian dialects are a group of West Germanic vernaculars, including Dutch and closely related varieties, spoken primarily in the Netherlands, northern Belgium, and adjacent regions of Germany.
-
D.
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.
-
E.
district of Hesse
A district of Hesse is an administrative subdivision within the German state of Hesse that encompasses multiple municipalities and towns for regional governance and public services.
- 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.