Triple
T26787620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raijua dialect |
E670428
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of the Sawu language |
C52043
|
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 variety of the Sawu language Context triple: [Raijua dialect, instanceOf, regional variety of the Sawu language]
-
A.
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.
-
B.
regional variety of Rejang language
A regional variety of the Rejang language is a geographically distinct form of Rejang characterized by unique phonological, lexical, and sometimes grammatical features while remaining mutually intelligible with other Rejang dialects.
-
C.
regional variety of the Sawai language
A regional variety of the Sawai language is a geographically or socially defined form of Sawai that differs from other forms in pronunciation, vocabulary, and/or grammar while remaining mutually intelligible.
-
D.
regional variety of the Kayan language
A regional variety of the Kayan language is a geographically distinct form of Kayan characterized by unique phonological, lexical, or grammatical features shared by speakers in a particular area.
-
E.
Bidayuh language variety
A Bidayuh language variety is a specific regional or community-based form of the Bidayuh language, characterized by distinct phonological, lexical, and grammatical features shared by its speakers.
- 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_69eeb31d45f8819089f52ebdbc556218 |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 4:13 a.m.