Triple
T7449277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tidore language |
E171963
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | North Halmahera 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: North Halmahera language Context triple: [Tidore language, instanceOf, North Halmahera language]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69c68a65402881908f7869368eb746fb |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:14 p.m.