Triple
T6981255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kelantan-Pattani Malay |
E161850
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional Malay dialect |
C20639
|
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: regional Malay dialect Context triple: [Kelantan-Pattani Malay, instanceOf, regional Malay dialect]
-
A.
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.
-
B.
regional language of Indonesia
A regional language of Indonesia is a native language spoken by a specific ethnic group or community within the Indonesian archipelago, distinct from the national language Bahasa Indonesia and used in local daily communication, culture, and traditions.
-
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.
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.
-
E.
Odia dialect
Odia dialect refers to any regional or social variety of the Odia language, characterized by distinct phonological, lexical, and syntactic features used by specific communities within Odisha and neighboring regions.
- 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_69c68855dc0481909b4c7e9e9ed273db |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:31 p.m.