Triple

T20557356
Position Surface form Disambiguated ID Type / Status
Subject Abaza E504752 entity
Predicate hasAlternativeName P39 FINISHED
Object Abaza 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: Abaza language | Statement: [Abaza, hasAlternativeName, Abaza language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Abaza language
Context triple: [Abaza, hasAlternativeName, Abaza 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. Abazin language
    The Abazin language is a Northwest Caucasian language spoken primarily by the Abazin people in the North Caucasus region of Russia and in diaspora communities.
  • C. Abaza chosen
    Abaza is a Northwest Caucasian language spoken primarily in the Russian Republic of Karachay-Cherkessia, known for its complex consonant system and rich verbal morphology.
  • D. Khazar language
    The Khazar language was the now-extinct Turkic tongue once spoken by the Khazar Khaganate, belonging to the Oghur branch of the Turkic language family.
  • E. Lezgian
    Lezgian is a Northeast Caucasian language spoken primarily by the Lezgin people in southern Dagestan and northern Azerbaijan.
  • 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_69e0b4b6587c8190aee63dc7cff244ea completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a5de9c008190b8620628fb285e90 completed April 20, 2026, 10:17 p.m.
Created at: April 16, 2026, 11:38 a.m.