Triple

T14676396
Position Surface form Disambiguated ID Type / Status
Subject Kökeqota E344657 entity
Predicate hasNameInMongolian P67727 FINISHED
Object Kökeqota E344657 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: Kökeqota | Statement: [Kökeqota, hasNameInMongolian, Kökeqota]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kökeqota
Context triple: [Kökeqota, hasNameInMongolian, Kökeqota]
  • A. Kökeqota chosen
    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.
  • B. Kökejin
    Kökejin was a Mongol noblewoman of the Yuan dynasty best known as the mother of Emperor Temür Khan.
  • C. Kocaali
    Kocaali is a coastal town and district in northwestern Turkey, situated along the Black Sea in Sakarya Province.
  • D. Uzkoye
    Uzkoye is a historic estate and former village in the south of Moscow, Russia, known for its noble residences and integration into the modern city.
  • E. Köchü
    Köchü was a 13th-century Mongol prince of the Borjigin dynasty, known as one of Ögedei Khan’s sons who held influence within the early Mongol Empire.
  • 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_69d822e34b348190ada4d1cdb6c7c226 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb5666e648190b5faa07076f497b8 completed April 14, 2026, 9:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdfb7c7df88190a4e551a12f6e8158 completed May 8, 2026, 3:04 p.m.
Created at: April 10, 2026, 1:27 a.m.