Triple
T31399394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Waigali |
E800952
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Waigali language |
C59382
|
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: variety of Waigali language Context triple: [Upper Waigali, instanceOf, variety of Waigali language]
-
A.
variety of Wapishana language
A variety of the Wapishana language is a distinct regional or social form of Wapishana, characterized by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other forms.
-
B.
variety of Lau language
A variety of Lau language is a distinct regional or social form of the Lau language characterized by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Lau forms.
-
C.
Mari language variety
A Mari language variety is a specific form or dialect of the Mari language, distinguished by its unique phonological, grammatical, and lexical features used by a particular Mari-speaking community.
-
D.
Noongar language variety
A Noongar language variety is a specific regional or dialectal form of the Noongar Aboriginal language spoken in southwestern Western Australia, characterized by distinct phonological, lexical, and grammatical features within the broader Noongar language continuum.
-
E.
variety of Siwu language
A variety of the Siwu language is a distinct regional or social form of Siwu characterized by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other forms.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
Created at: April 29, 2026, 9:19 p.m.