Triple
T13068003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilocos Sur |
E329377
|
entity |
| Predicate | hasLocalLanguage |
P4185
|
FINISHED |
| Object | Kankanay |
E581931
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Kankanay | Statement: [Ilocos Sur, hasLocalLanguage, Kankanay]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kankanay Context triple: [Ilocos Sur, hasLocalLanguage, Kankanay]
-
A.
Kankanay
chosen
Kankanay is an Austronesian language spoken by the Kankanaey people of the northern Philippines, particularly in the Cordillera region of Luzon.
-
B.
K’ana
K’ana is an alternative name for Espinar Province, a highland administrative region in the Cusco Department of southern Peru known for its Andean culture and mining activities.
-
C.
Kanembu
The Kanembu are an ethnic group of the Lake Chad region, historically linked to the ruling elite and culture of the medieval Kanem-Bornu Empire.
-
D.
Kandas
Kandas is an Oceanic language of the Meso-Melanesian subgroup spoken in parts of Papua New Guinea.
-
E.
Kanyok
Kanyok is a Bantu language spoken primarily by the Kanyok people in the Democratic Republic of the Congo.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980ec8ba48190baf52c7823482680 |
completed | April 10, 2026, 10:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6d603419c8190b8d1726365db59dc |
completed | May 3, 2026, 4:58 a.m. |
Created at: April 9, 2026, 9 p.m.