Triple
T4005833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch Low Saxon |
E89523
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Low German dialect continuum |
C1720
|
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 continuum Context triple: [Dutch Low Saxon, instanceOf, Low German dialect continuum]
-
A.
dialect continuum
chosen
A dialect continuum is a range of geographically adjacent language varieties that change gradually from one area to the next, so that neighboring dialects are mutually intelligible but those at distant ends may not be.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:34 p.m.