Triple
T23602731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selako Bidayuh |
E582804
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bidayuh language variety |
C47856
|
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: Bidayuh language variety Context triple: [Selako Bidayuh, instanceOf, Bidayuh language variety]
-
A.
Sambal language variety
Sambal language variety is a specific form or dialect of the Sambal language, characterized by distinct phonological, lexical, and grammatical features used by a particular Sambal-speaking community.
-
B.
Subanen language variety
A Subanen language variety is a specific regional or social form of the Subanen language spoken by Subanen communities in the Zamboanga Peninsula and surrounding areas of the southern Philippines, characterized by distinct phonological, lexical, and grammatical features.
-
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.
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.
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.
- 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_69e248faa2788190abb1581742daa6aa |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:43 p.m.