Triple
T24084483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ambaguio Kallahan |
E596597
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of the Kalanguya language |
C48604
|
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 Kalanguya language Context triple: [Ambaguio Kallahan, instanceOf, variety of the Kalanguya language]
-
A.
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.
-
B.
variety of the Kayan language
A variety of the Kayan language is a distinct regional or social form of Kayan characterized by its own phonological, lexical, and grammatical features while remaining mutually intelligible to varying degrees with other Kayan varieties.
-
C.
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.
-
D.
Kayan language variety
A Kayan language variety is a specific linguistic form or dialect within the Kayan language family, spoken by Kayan communities and characterized by its own phonological, lexical, and grammatical features.
-
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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 10:44 p.m.