Triple

T3451349
Position Surface form Disambiguated ID Type / Status
Subject Kyrgyz E72799 entity
Predicate hasStandardForm P103 FINISHED
Object Standard Kyrgyz E72799 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: Standard Kyrgyz | Statement: [Kyrgyz, hasStandardForm, Standard Kyrgyz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Standard Kyrgyz
Context triple: [Kyrgyz, hasStandardForm, Standard Kyrgyz]
  • A. Kyrgyz chosen
    Kyrgyz is a Turkic language primarily spoken in Kyrgyzstan and surrounding regions of Central Asia.
  • B. Kazakh language
    The Kazakh language is a Turkic language spoken primarily in Kazakhstan and surrounding regions, written today mainly in Cyrillic but also in Latin and Arabic scripts.
  • C. Saryk dialect
    The Saryk dialect is a regional variety of the Turkmen language traditionally spoken by the Saryk Turkmen people of Central Asia.
  • D. Turkmen language
    The Turkmen language is a Turkic language spoken primarily in Turkmenistan and surrounding regions, closely related to Turkish and other Oghuz languages.
  • E. Kyrgyz Canadian
    A Kyrgyz Canadian is a Canadian resident or citizen of ethnic Kyrgyz origin, typically with cultural roots in Kyrgyzstan and connections to the broader Kyrgyz diaspora.
  • 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_69ad85b12a908190a1d10a6b03b4f8ae completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adba7465248190947f9096e230e1c4 completed March 8, 2026, 6:05 p.m.
NED1 Entity disambiguation (via context triple) batch_69b360ef69308190a11f37ddbf3bbc7b completed March 13, 2026, 12:57 a.m.
Created at: March 8, 2026, 3:16 p.m.