Triple

T11343225
Position Surface form Disambiguated ID Type / Status
Subject Ulak tartysh E268651 entity
Predicate hasAlternativeName P39 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: [Ulak tartysh, hasAlternativeName, kok boru]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: kok boru
Context triple: [Ulak tartysh, hasAlternativeName, 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 was the abbreviated name of the People's Security Agency, an early post-World War II Indonesian security and defense organization.
  • D. Kok
    Kok is a Dutch surname most notably borne by Wim Kok, a former Prime Minister of the Netherlands.
  • E. BK
    BK is a common abbreviation for Brooklyn, a borough of New York City known for its cultural diversity, arts scene, and historic neighborhoods.
  • 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_69d6aacb1f0881908c84a349fd1be047 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7ea1e360c8190a02d1e2d1d6f4b5d completed April 9, 2026, 6:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69e5435f4e288190b9b0029dc35bf2c5 completed April 19, 2026, 9:04 p.m.
Created at: April 8, 2026, 9:33 p.m.