Triple
T6565149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sambas Malay |
E153884
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Malayic language variety |
C20292
|
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: Malayic language variety Context triple: [Sambas Malay, instanceOf, Malayic language variety]
-
A.
Yana language variety
Yana language variety refers to any of the related but distinct forms of the Yana language traditionally spoken by the Yana people of northern California, encompassing dialectal differences in phonology, vocabulary, and grammar.
-
B.
Nicobarese language variety
A Nicobarese language variety is a specific linguistic form or dialect within the Nicobarese branch of the Austroasiatic language family, spoken by the indigenous Nicobarese people of India’s Nicobar Islands.
-
C.
Gondi language variety
A Gondi language variety is a specific regional or social form of the Gondi language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader Dravidian language continuum.
-
D.
regional variety of the Javanese language
A regional variety of the Javanese language is a geographically distinct form of Javanese characterized by unique phonological, lexical, and sometimes grammatical features while remaining mutually intelligible with other Javanese varieties.
-
E.
Malay-based creole
chosen
A Malay-based creole is a stable contact language that developed from Malay as its primary lexical source, mixed with grammatical and lexical influences from other languages, and used as a native or community language.
- 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_69c6880cb35881909b763eb0125236b9 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 1:52 p.m.