Triple
T10489406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karanga language |
E247374
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Maban language |
C22855
|
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: Maban language Context triple: [Karanga language, instanceOf, Maban language]
-
A.
Munda language
The Munda language is a member of the Austroasiatic language family spoken primarily by indigenous Munda communities in eastern and central India, characterized by agglutinative morphology and distinct phonological features.
-
B.
Batanic language
The Batanic language is a subgroup of Austronesian languages spoken primarily in the Batanes Islands of the northern Philippines and nearby areas, characterized by shared phonological and lexical features distinct from neighboring Philippine languages.
-
C.
Misumalpan language
Misumalpan language is a small family of indigenous languages spoken primarily along the Atlantic coast of Nicaragua and neighboring regions, including Miskito, Sumo (Mayangna), and Matagalpan varieties.
-
D.
Ubangian language
chosen
A Ubangian language is a member of a proposed group of Central African languages, primarily spoken in the Central African Republic and neighboring countries, that share common phonological and grammatical features and are often considered a branch of the Niger-Congo family.
-
E.
Nobiin language
Nobiin language is a Northern Nubian language of the Nilo-Saharan family spoken primarily along the Nile in southern Egypt and northern Sudan, notable for its rich oral tradition and historical significance in Nubian culture.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:23 p.m.