Triple
T10483256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pokot |
E247224
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Pekot |
E868983
|
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: Pekot | Statement: [Pokot, hasAlternativeName, Pekot]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pekot Context triple: [Pokot, hasAlternativeName, Pekot]
-
A.
Pekar
Pekar is a surname of Central or Eastern European origin, notably associated with several cultural and artistic figures.
-
B.
Pekat
Pekat is a settlement on the Indonesian island of Sumbawa that was devastated by the catastrophic 1815 eruption of Mount Tambora.
-
C.
Pecile
Pecile is a large colonnaded garden and pool complex within Hadrian’s Villa at Tivoli, designed as a central courtyard for leisure, reflection, and display of imperial grandeur.
-
D.
Pökoot
chosen
Pökoot is a Nilotic language spoken primarily by the Pokot people in Kenya and Uganda.
-
E.
Pochutec
Pochutec is an extinct Uto-Aztecan language once spoken in the Pochutla region of Oaxaca, Mexico.
- 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_69d933c5caa08190a5fba92ebf4b0ff9 |
completed | April 10, 2026, 5:30 p.m. |
Created at: April 6, 2026, 12:22 p.m.