Triple
T25844904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooke’s Point Palawano language |
E651038
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Palawano language variety |
C50792
|
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: Palawano language variety Context triple: [Brooke’s Point Palawano language, instanceOf, Palawano language variety]
-
A.
Ivatan language variety
A specific form or dialect of the Ivatan language, characterized by its unique phonological, lexical, and grammatical features within the Ivatan-speaking community.
-
B.
Visayan language variety
A Visayan language variety is a specific regional or social form of any language within the Visayan (Bisayan) subgroup of the Austronesian language family, characterized by distinct phonological, lexical, and grammatical features.
-
C.
Kalinga language variety
A Kalinga language variety is a specific regional or ethnolinguistic form of the Kalinga language spoken in the Cordillera region of the northern Philippines, characterized by distinct phonological, lexical, and grammatical features.
-
D.
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.
-
E.
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.
- 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_69e7ab38086081908f3a8e7e0c6efd83 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 7:52 a.m.