Triple
T24626640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nusa Laut language |
E609558
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Central Maluku language |
C48526
|
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: Central Maluku language Context triple: [Nusa Laut language, instanceOf, Central Maluku language]
-
A.
South Sulawesi language
A South Sulawesi language is a member of a subgroup of the Austronesian language family spoken primarily in South Sulawesi, Indonesia, characterized by shared phonological, grammatical, and lexical features distinct to this regional cluster.
-
B.
Papuan language
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.
-
C.
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.
-
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. 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_69e2c4d1d3708190a0f2dc6a3a8523bb |
completed | April 17, 2026, 11:40 p.m. |
Created at: April 18, 2026, 2:32 a.m.