Triple
T31708398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oepao language |
E809247
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Timoric language |
C57853
|
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: Timoric language Context triple: [Oepao language, instanceOf, Timoric language]
-
A.
Sumba language
The Sumba language is an Austronesian language (or group of closely related languages) spoken by the indigenous people of Sumba Island in eastern Indonesia, characterized by diverse dialects and rich oral traditions.
-
B.
Taracahitic language
A Taracahitic language is a member of a subgroup of the Uto-Aztecan language family spoken in northwestern Mexico, characterized by shared phonological and grammatical features among its constituent languages.
-
C.
Batak language
Batak language is a group of closely related Austronesian languages spoken by the Batak peoples of North Sumatra, Indonesia, each with its own dialects and traditional writing system.
-
D.
Malaitan language
Malaitan language is a conceptual class representing any of the closely related Austronesian languages spoken on Malaita Island in the Solomon Islands, characterized by shared phonological, grammatical, and lexical features within the Southeast Solomonic subgroup.
-
E.
Ubangian language
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.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:14 p.m.