Triple
T24756830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nalik–Notsi subgroup |
E619310
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of Western Bismarck languages |
C49125
|
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: branch of Western Bismarck languages Context triple: [Nalik–Notsi subgroup, instanceOf, branch of Western Bismarck languages]
-
A.
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.
-
B.
branch of the Turkic languages
A branch of the Turkic languages is a subgroup of related Turkic languages that share a common historical origin, structural features, and vocabulary within the broader Turkic language family.
-
C.
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.
-
D.
branch of Nilo-Saharan languages
A branch of Nilo-Saharan languages is a subgroup within the proposed Nilo-Saharan language family, consisting of related languages that share common historical origins and linguistic features.
-
E.
branch of Bantu languages
A branch of Bantu languages is a subgroup within the Bantu language family whose member languages share a common historical origin and exhibit closely related grammatical, phonological, and lexical features.
- F. None of above. chosen
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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 4:26 a.m.