Triple
T23529929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saribas Iban |
E576535
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Iban language variety |
C47193
|
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: Iban language variety Context triple: [Saribas Iban, instanceOf, Iban language variety]
-
A.
Iban language
chosen
The Iban language is an Austronesian language spoken primarily by the Iban people of Sarawak in Malaysian Borneo, known for its rich oral tradition and use in both everyday communication and cultural practices.
-
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.
Sabaic language variety
A Sabaic language variety is a specific form or dialect of the ancient South Arabian Sabaic language, distinguished by its unique linguistic features, geographic distribution, and historical context within the Sabaean cultural sphere.
-
D.
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.
-
E.
Luri language variety
A Luri language variety is a specific regional or social form of the Luri language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader continuum of Southwestern Iranian dialects.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 6:09 p.m.