Triple
T4221853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jarawa language |
E94357
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ongan language |
C12061
|
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: Ongan language Context triple: [Jarawa language, instanceOf, Ongan language]
-
A.
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.
-
B.
Central Tano language
A Central Tano language is a member of the Tano branch of the Niger-Congo language family spoken primarily in Ghana and neighboring regions, characterized by tonal phonology and shared grammatical and lexical features with related Akanic and Guang languages.
-
C.
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.
-
D.
Great Andamanese language
chosen
The Great Andamanese language is an endangered mixed language spoken by the indigenous Great Andamanese people of the Andaman Islands, combining elements from several original Andamanese languages with influences from Hindi and other contact languages.
-
E.
Khoe language
The Khoe language is a member of the Khoe-Kwadi family of southern African languages, traditionally spoken by Khoe pastoralist and hunter-gatherer communities and characterized by distinctive click consonants and rich tonal patterns.
- 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_69b3451997e08190851db4a9a588837d |
completed | March 12, 2026, 10:58 p.m. |
Created at: March 12, 2026, 11:04 p.m.