Triple
T25577306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paraujano language |
E641142
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Maipurean language |
C50964
|
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: Maipurean language Context triple: [Paraujano language, instanceOf, Maipurean language]
-
A.
Tamanic language
A Tamanic language is a member of a small subgroup of Austronesian languages spoken primarily in Borneo, characterized by shared phonological and lexical features that distinguish them from neighboring language groups.
-
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.
Kayanic language
A Kayanic language is a member of a subgroup of Austronesian languages spoken primarily by the Kayan, Kenyah, and related peoples of Borneo, characterized by shared phonological, lexical, and grammatical features distinct within the Greater North Borneo branch.
-
D.
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.
-
E.
Mosetenan language
The Mosetenan language is an indigenous language family of Bolivia, primarily spoken by the Mosetén and Chimane peoples in the Amazonian lowlands, known for its complex verb morphology and endangered status.
- 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 4:02 p.m.