Triple
T2886277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pangasinan language |
E59513
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Northern Luzon language |
C5376
|
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: Northern Luzon language Context triple: [Pangasinan language, instanceOf, Northern Luzon language]
-
A.
Central Luzon language
chosen
A Central Luzon language is a member of a subgroup of Philippine Austronesian languages spoken primarily in the Central Luzon region of the Philippines, characterized by shared phonological, grammatical, and lexical features distinct from other Philippine language groups.
-
B.
Tai language
A Tai language is a member of the Tai branch of the Kra–Dai language family, characterized by tonal phonology and analytic grammar, spoken primarily in Southeast Asia by Tai ethnic groups.
-
C.
Banda languages
Banda languages are a group of closely related Ubangian languages spoken primarily in the Central African Republic and neighboring regions, characterized by shared phonological and grammatical features.
-
D.
Quechuan language
A Quechuan language is any member of a family of indigenous languages of the Andes, primarily spoken in Peru, Bolivia, Ecuador, Colombia, and Argentina, that share common grammatical structures and vocabulary derived from a Proto-Quechuan ancestor.
-
E.
Chibchan language
A Chibchan language is a member of a family of indigenous languages spoken primarily in Central America and northern South America, characterized by shared grammatical and phonological features reflecting a common ancestral origin.
- 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_69ab4ac739188190a112f42a5a69c951 |
completed | March 6, 2026, 9:44 p.m. |
Created at: March 6, 2026, 10:03 p.m.