Triple
T17082588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weser-Rhine Germanic languages |
E414511
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hypothesized language subgroup |
C14762
|
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: hypothesized language subgroup Context triple: [Weser-Rhine Germanic languages, instanceOf, hypothesized language subgroup]
-
A.
hypothesized language group
chosen
A hypothesized language group is a proposed set of languages believed to share a common ancestor based on comparative evidence, but whose genetic relationship has not yet been conclusively demonstrated or widely accepted.
-
B.
language family subgroup
A language family subgroup is a set of closely related languages within a larger language family that share a more recent common ancestor and distinctive linguistic features.
-
C.
Munda languages subgroup
The Munda languages subgroup is a branch of the Austroasiatic language family spoken primarily in eastern and central India, characterized by agglutinative morphology and distinctive phonological and syntactic features.
-
D.
Yuman language subgroup
The Yuman language subgroup is a branch of the Yuman–Cochimí language family comprising closely related Indigenous languages spoken primarily along the lower Colorado River, in southwestern Arizona, southeastern California, and northern Baja California.
-
E.
subgroup of Mayan languages
A subgroup of Mayan languages is a set of closely related Mayan languages that share a common ancestral branch within the Mayan language family, characterized by shared phonological, grammatical, and lexical innovations.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:35 a.m.