Triple
T24366315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pijin (Solomon Islands) |
E614203
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Melanesian pidgin |
C48382
|
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: Melanesian pidgin Context triple: [Pijin (Solomon Islands), instanceOf, Melanesian pidgin]
-
A.
Nauruan language
The Nauruan language is an Austronesian language spoken primarily on the Pacific island nation of Nauru, characterized by its unique phonology and limited number of speakers.
-
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.
Chuukic language
The Chuukic language is a group of closely related Micronesian languages spoken primarily in the Chuuk State of the Federated States of Micronesia and surrounding regions, characterized by shared phonological and grammatical features within the Oceanic branch of the Austronesian language family.
-
D.
Niuean language
Niuean language is a Polynesian language spoken primarily on the island nation of Niue and among Niuean communities in New Zealand, characterized by its Austronesian roots and close relation to Tongan and Samoan.
-
E.
regional variety of Mortlockese
A regional variety of Mortlockese is a localized form of the Mortlockese language distinguished by area-specific pronunciation, vocabulary, and sometimes grammar used within particular islands or communities in the Mortlock Islands.
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:01 a.m.