Triple
T4564027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Franconian dialects |
E121864
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | East Franconian dialects |
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: East Franconian dialects Context triple: [Upper Franconian dialects, instanceOf, East Franconian dialects]
-
A.
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.
-
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.
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.
-
D.
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.
-
E.
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.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 1:09 p.m.