Triple
T14453171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyrgyz people |
E358387
|
entity |
| Predicate | traditionalSport |
P8417
|
FINISHED |
| Object | kok boru |
E84249
|
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: kok boru | Statement: [Kyrgyz people, traditionalSport, kok boru]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: kok boru Context triple: [Kyrgyz people, traditionalSport, kok boru]
-
A.
Kok-boru
chosen
Kok-boru is a traditional Central Asian horseback team game, similar to polo, in which riders compete to carry and score with a goat or sheep carcass.
-
B.
BKR
BKR is the postal code prefix used for addresses in the town of Birkirkara in Malta.
-
C.
BKR
BKR is the station code for Beckenham Road tram stop on the Tramlink network in south London, England.
-
D.
BKR
BKR was the abbreviated name of the People's Security Agency, an early post-World War II Indonesian security and defense organization.
-
E.
Kok
Kok is a Dutch surname most notably borne by Wim Kok, a former Prime Minister of the Netherlands.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91a8bf088190abf5fd4f646b8c62 |
completed | April 14, 2026, 7:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd648f56608190b6d55c592c088575 |
completed | May 8, 2026, 4:20 a.m. |
Created at: April 10, 2026, 1:19 a.m.