Triple
T16579140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banten Javanese |
E402792
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Javanese dialect |
C18008
|
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: Javanese dialect Context triple: [Banten Javanese, instanceOf, Javanese dialect]
-
A.
regional variety of the Javanese language
chosen
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.
regional variety of the Sasak language
A regional variety of the Sasak language is a geographically and socially distinct form of Sasak characterized by systematic differences in pronunciation, vocabulary, and grammar from other Sasak varieties.
-
D.
regional Malay dialect
A regional Malay dialect is a localized variety of the Malay language characterized by distinct phonological, lexical, and grammatical features shaped by the specific geographic, historical, and cultural context of its speakers.
-
E.
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.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:16 a.m.