Triple
T9733196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalibo |
E235994
|
entity |
| Predicate | languageSpoken |
P151
|
FINISHED |
| Object | Aklanon |
E104740
|
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: Aklanon | Statement: [Kalibo, languageSpoken, Aklanon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aklanon Context triple: [Kalibo, languageSpoken, Aklanon]
-
A.
Aklanon
chosen
Aklanon is an Austronesian language spoken primarily in the province of Aklan in the central Philippines.
-
B.
Aklan
Aklan is a province in the Philippines known for the world-famous Boracay Island and its vibrant Ati-Atihan Festival.
-
C.
Apayao
Apayao is a landlocked, mountainous province in the northern Philippines known for its rich indigenous culture, forests, and river systems.
-
D.
Talisay
Talisay is a city in the Philippine province of Negros Occidental known for its sugarcane industry and historical landmarks.
-
E.
Talisay
Talisay is a coastal municipality in the Philippine province of Camarines Norte known for its rural communities and access to fishing and agricultural resources.
- 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9eb54fe481908b0202f104b75dc1 |
completed | April 1, 2026, 10:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2fff34bb08190bebd5089324782dd |
completed | April 6, 2026, 12:36 a.m. |
Created at: March 30, 2026, 8:22 p.m.