Triple

T20462029
Position Surface form Disambiguated ID Type / Status
Subject Buynaksk dialect E501947 entity
Predicate partOf P40 FINISHED
Object Kumyk 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: Kumyk language | Statement: [Buynaksk dialect, partOf, Kumyk language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kumyk language
Context triple: [Buynaksk dialect, partOf, Kumyk language]
  • A. 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.
  • B. Kumzari language
    The Kumzari language is an endangered Southwestern Iranian language spoken primarily by the Kumzari people in the Musandam Peninsula of Oman.
  • C. Tsakhur language
    The Tsakhur language is a Northeast Caucasian language spoken primarily by the Tsakhur people in parts of Azerbaijan and Dagestan.
  • D. Kuyumeri language
    The Kuyumeri language is an indigenous tongue of the Harakmbut people of the Peruvian Amazon, belonging to the broader Harakmbut language family.
  • E. Kumyk chosen
    Kumyk is a Turkic language traditionally spoken by the Kumyk people in the North Caucasus region, particularly in present-day 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_69e0b4ad4940819098cf2ff6413574e5 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e696a761648190b24cf4bb90a8abb1 completed April 20, 2026, 9:12 p.m.
Created at: April 16, 2026, 11:33 a.m.