Triple
T21714304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mabaka Valley Kalinga |
E535983
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of the Kalinga language |
C44743
|
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 Kalinga language Context triple: [Mabaka Valley Kalinga, instanceOf, variety of the Kalinga language]
-
A.
Kalinga language variety
chosen
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.
-
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.
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.
-
D.
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.
-
E.
variety of Cebuano language
A variety of Cebuano language is a regional or social form of Cebuano distinguished by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other forms.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:47 p.m.