Triple
T3441541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gutnish |
E72575
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | North Germanic language variety |
C4118
|
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: North Germanic language variety Context triple: [Gutnish, instanceOf, North Germanic language variety]
-
A.
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.
-
B.
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.
-
C.
branch of the Germanic languages
A branch of the Germanic languages is a subgroup of related Germanic languages that share a common historical origin, structural features, and vocabulary, such as the North, West, or (extinct) East Germanic branches.
-
D.
North Germanic people
North Germanic people are an ethnolinguistic group in Northern Europe who historically spoke North Germanic (Scandinavian) languages and share related cultural, historical, and genetic heritage.
-
E.
West Nordic language
chosen
A West Nordic language is a North Germanic language variety spoken in the western Nordic region, primarily including Icelandic, Faroese, and sometimes Norwegian dialects with shared historical and structural features.
- 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:16 p.m.