Triple
T5197978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ripuarian |
E117319
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German dialect continuum variety |
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: German dialect continuum variety Context triple: [Ripuarian, instanceOf, German dialect continuum variety]
-
A.
dialect continuum
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.
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.
-
D.
West Germanic language
A West Germanic language is a member of the Germanic branch of the Indo-European language family that evolved in western and central Europe, including languages such as English, German, and Dutch.
-
E.
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.
- 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_69bd4462ed04819084fcb01eb9d2fa74 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:47 p.m.