Triple

T19448746
Position Surface form Disambiguated ID Type / Status
Subject Noʻkis E486555 entity
Predicate hasNameInLanguage P15 FINISHED
Object Karakalpak language NE NERFINISHED

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: Karakalpak language | Statement: [Noʻkis, hasNameInLanguage, Karakalpak language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Karakalpak language
Context triple: [Noʻkis, hasNameInLanguage, Karakalpak language]
  • A. Karakalpak language chosen
    The Karakalpak language is a Turkic language spoken primarily by the Karakalpak people in Karakalpakstan, an autonomous republic within Uzbekistan.
  • B. Karakhani language
    The Karakhani language was a historical Turkic language of the Karluk branch, associated with the Karakhanid Khanate in Central Asia.
  • C. Khinalug language
    The Khinalug language is a highly endangered Northeast Caucasian language spoken by the Khinalug people in a single mountain village in northern Azerbaijan.
  • D. Tajik language
    The Tajik language is a variety of Persian spoken primarily in Tajikistan and written in the Cyrillic script.
  • E. Karata language
    The Karata language is a Northeast Caucasian language spoken by the Karata people in the Republic of Dagestan, Russia.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8d7ad488190a3373045029b0f3b completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6338be5a48190973d9ecae853900c completed April 20, 2026, 2:09 p.m.
Created at: April 10, 2026, 1:38 p.m.