Triple
T5665649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Frisian Low Saxon |
E124850
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Low German dialect |
C18550
|
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: Low German dialect Context triple: [East Frisian Low Saxon, instanceOf, Low German dialect]
-
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.
Dutch dialect
A Dutch dialect is a regional or social variety of the Dutch language characterized by distinct pronunciation, vocabulary, and grammar used by speakers in specific areas or communities.
-
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.
Baltic German
A Baltic German is a member of the historically German-speaking minority that lived in the Baltic region (primarily present-day Estonia and Latvia), often forming part of the local urban elite and nobility from medieval times until the 20th century.
-
E.
Frisian language
Frisian language is a closely related group of West Germanic languages spoken primarily in the Friesland region of the Netherlands and parts of Germany, known for being the closest living relatives to English.
- 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_69c00828906881908966f270b8f130cf |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:43 p.m.