Triple
T24757606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kâte language |
E619334
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Papuan language of wider communication |
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: Papuan language of wider communication Context triple: [Kâte language, instanceOf, Papuan language of wider communication]
-
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.
Papuan Tip languages
Papuan Tip languages are a subgroup of Oceanic languages spoken at the southeastern tip of New Guinea and nearby islands, characterized by shared phonological and grammatical features distinct from other Oceanic branches.
-
C.
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.
-
D.
Melanesian pidgin
Melanesian pidgin is a group of English-based creole languages spoken across Melanesia that serve as lingua francas among diverse indigenous communities.
-
E.
Central Maluku language
A Central Maluku language is a member of a subgroup of Austronesian languages spoken in the central region of the Maluku Islands in eastern Indonesia, characterized by shared phonological, grammatical, and lexical features.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 4:26 a.m.