Triple
T25846740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bunak language |
E651090
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Timor–Alor–Pantar language |
C19241
|
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: Timor–Alor–Pantar language Context triple: [Bunak language, instanceOf, Timor–Alor–Pantar language]
-
A.
Papuan language
chosen
A Papuan language is any of the numerous non-Austronesian, non-Australian indigenous languages spoken primarily on the island of New Guinea and neighboring regions, representing several distinct and often unrelated language families.
-
B.
Minahasan language
The Minahasan language is an Austronesian language (or group of closely related dialects) traditionally spoken by the Minahasan people of North Sulawesi, Indonesia, characterized by complex verbal morphology and significant influence from Malay/Indonesian.
-
C.
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.
-
D.
Dayak language
Dayak language refers to any of the indigenous Austronesian languages spoken by the Dayak peoples of Borneo, encompassing numerous distinct but related linguistic varieties across Indonesia and Malaysia.
-
E.
Sama–Bajaw language
The Sama–Bajaw language is a group of closely related Austronesian languages spoken by the seafaring Sama-Bajau peoples across maritime Southeast Asia, particularly in the Philippines, Malaysia, and Indonesia.
- 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_69e7ab38086081908f3a8e7e0c6efd83 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 7:53 a.m.