Triple
T12116637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frisian (Westerkwartiers dialect) |
E288579
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of West Frisian |
C6815
|
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: regional variety of West Frisian Context triple: [Frisian (Westerkwartiers dialect), instanceOf, regional variety of West Frisian]
-
A.
Frisian language
chosen
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.
-
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.
regional variety of Polish
A regional variety of Polish is a geographically localized form of the Polish language characterized by distinct pronunciation, vocabulary, and sometimes grammar that reflect the cultural and historical influences of a specific area.
-
D.
regional variety of the Breton language
A regional variety of the Breton language is a geographically defined form of Breton characterized by distinct phonological, lexical, and sometimes grammatical features that differentiate it from other Breton dialects.
-
E.
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.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:49 p.m.