Triple
T23993770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bak languages |
E605136
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Atlantic languages subgroup |
C4276
|
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: Atlantic languages subgroup Context triple: [Bak languages, instanceOf, Atlantic languages subgroup]
-
A.
Atlantic language
Atlantic language is a member of a branch of the Niger-Congo language family spoken primarily along the Atlantic coast of West Africa, characterized by diverse phonological systems and noun class structures.
-
B.
language family subgroup
chosen
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.
Atlantic English-lexifier creole
An Atlantic English-lexifier creole is a creole language that developed around the Atlantic basin with English as its primary lexical source, typically arising from prolonged contact between English speakers and diverse African and other populations in colonial and postcolonial settings.
-
D.
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.
-
E.
Saxon subgroup
A Saxon subgroup is a subgroup of a group that satisfies specific structural or algebraic conditions related to the behavior of its elements under conjugation and interaction with other subgroups, often studied in the context of finite group theory.
- 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 17, 2026, 9:38 p.m.