Triple
T1112521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limburgish (Dutch variety) |
E11026
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Low Franconian dialect |
C243
|
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 Franconian dialect Context triple: [Limburgish (Dutch variety), instanceOf, Low Franconian dialect]
-
A.
Alpine language
Alpine language is a conceptual class representing any linguistic system that has evolved within or is predominantly used in mountainous Alpine regions, shaped by their geography, culture, and historical isolation.
-
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.
Oïl language
An Oïl language is any of a group of closely related Romance languages and dialects historically spoken in northern France, Belgium, and the Channel Islands, characterized by the use of "oïl" (modern "oui") for "yes."
-
D.
West Germanic language
chosen
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.
Eastern Romance language
An Eastern Romance language is a member of the Romance branch of the Indo-European language family that evolved from Eastern varieties of Vulgar Latin, primarily spoken in the Balkans and surrounding regions.
- 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:43 p.m.