Triple
T10483257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pokot |
E247224
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Pökot |
E247224
|
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: Pökot | Statement: [Pokot, hasAlternativeName, Pökot]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pökot Context triple: [Pokot, hasAlternativeName, Pökot]
-
A.
Pökoot
Pökoot is a Nilotic language spoken primarily by the Pokot people in Kenya and Uganda.
-
B.
Bompoka
Bompoka is a small, remote island that forms part of India’s Nicobar Islands archipelago in the eastern Indian Ocean.
-
C.
Pokot
chosen
Pokot is a Southern Nilotic language spoken primarily by the Pokot people of Kenya and eastern Uganda.
-
D.
Kökeqota
Kökeqota is a historic city in what is now Hohhot, Inner Mongolia, that served as the principal political and administrative center of the Northern Yuan dynasty after the fall of the Yuan in China.
-
E.
Pákozd
Pákozd is a Hungarian village in Fejér County known for its proximity to Lake Velence and its historical significance, including an important 1848 revolutionary battle.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509678ac88190984f18a2162e2dcf |
completed | April 7, 2026, 1:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d94b0d05a88190be036a6e4ab374a7 |
completed | April 10, 2026, 7:10 p.m. |
Created at: April 6, 2026, 12:22 p.m.