Triple
T29775406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maliku |
E755364
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of the Lawangan language |
C55691
|
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 the Lawangan language Context triple: [Maliku, instanceOf, variety of the Lawangan language]
-
A.
variety of the Kalanguya language
A variety of the Kalanguya language is a regional or social form of Kalanguya distinguished by unique phonological, lexical, or grammatical features used by a particular speech community.
-
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.
Palawano language variety
A Palawano language variety is a specific regional or ethnolinguistic form of the Palawano Austronesian language spoken by distinct Palawano communities on the island of Palawan in the Philippines.
-
D.
variety of the Aralle-Tabulahan language
A variety of the Aralle-Tabulahan language is a distinct regional or social form of this Austronesian language, characterized by its own specific phonological, lexical, or grammatical features while remaining mutually intelligible with other Aralle-Tabulahan varieties.
-
E.
variety of the Isinay language
A variety of the Isinay language is a regional or social form of Isinay distinguished 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 8:45 p.m.