Triple

T15759025
Position Surface form Disambiguated ID Type / Status
Subject Turki E382043 entity
Predicate closelyRelatedTo P37 FINISHED
Object Old Uzbek E388720 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: Old Uzbek | Statement: [Turki, closelyRelatedTo, Old Uzbek]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Old Uzbek
Context triple: [Turki, closelyRelatedTo, Old Uzbek]
  • A. Bukharic
    Bukharic is a Jewish dialect of Tajik spoken historically by the Bukharan Jewish community of Central Asia.
  • B. Oghuz Uzbek
    Oghuz Uzbek refers to a historical Turkic group associated with the Oghuz branch that played a key role in the ethnogenesis of the Uzbek people.
  • C. Uzbek
    Uzbek refers to a Turkic ethnic group primarily associated with Uzbekistan and surrounding regions of Central Asia, known for their distinct language, culture, and historical heritage.
  • D. Khwarezmian language
    The Khwarezmian language was an extinct East Iranian language once spoken in the historical region of Khwarezm, in present-day Central Asia.
  • E. Qipchaq Uzbek chosen
    Qipchaq Uzbek is a variety of the Uzbek language that reflects strong Kipchak Turkic linguistic features, distinguishing it from the more widely known Oghuz-influenced standard Uzbek.
  • 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_69d86d9e6b44819085d1f6a969ecb74c completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e050b35ea48190a758ee76a57b5451 completed April 16, 2026, 3 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff8774eda08190a6231b4fd5027e6f completed May 9, 2026, 7:13 p.m.
Created at: April 10, 2026, 4:47 a.m.