Triple
T14401406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varanger Kven |
E357078
|
entity |
| Predicate | hasDialectalFeaturesSharedWith |
P114100
|
FINISHED |
| Object | other Kven dialects |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: other Kven dialects | Statement: [Varanger Kven, hasDialectalFeaturesSharedWith, other Kven dialects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDialectalFeaturesSharedWith Context triple: [Varanger Kven, hasDialectalFeaturesSharedWith, other Kven dialects]
-
A.
hasDialectContinuumWith
Indicates that two languages or dialects are part of a continuous chain of mutually intelligible varieties, without a clear boundary separating them.
-
B.
hasCommonLoanwordsFrom
Indicates that two languages share loanwords that originate from the same source language.
-
C.
consideredDialectOf
Indicates that one language variety is regarded as a dialect of another language or linguistic standard.
-
D.
sharesLinguisticFamilyWith
Indicates that two languages belong to the same linguistic family or branch within a language family.
-
E.
hasNumberOfDialects
Indicates the relationship between a language (or linguistic entity) and the count of distinct dialects it possesses.
- F. None of above. chosen
Provenance (4 batches)
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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de908500048190bb6a20fe318d5c62 |
completed | April 14, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
| PDg | Predicate description generation | batch_69de2e08b6c08190bb4c929deab236a6 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:17 a.m.