Triple

T21662617
Position Surface form Disambiguated ID Type / Status
Subject Tuvans E534630 entity
Predicate language P15 FINISHED
Object Tuvan 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: Tuvan language | Statement: [Tuvans, language, Tuvan language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tuvan language
Context triple: [Tuvans, language, Tuvan language]
  • A. Tuvan chosen
    Tuvan is a Turkic language spoken primarily in the Tuva Republic of Russia, known for its rich oral traditions and association with Tuvan throat singing.
  • B. Altai language
    The Altai language is a Turkic language spoken primarily in Russia’s Altai Republic and surrounding regions by the indigenous Altai people.
  • C. Sakha language
    The Sakha language is a Turkic language spoken primarily by the Sakha (Yakut) people in northeastern Siberia, where it serves as a major regional and cultural language.
  • D. Chulym language
    The Chulym language is a critically endangered Turkic language spoken by a small indigenous community in Siberia, Russia.
  • E. Khakas language
    Khakas language is a Turkic language spoken primarily by the Khakas people in the Republic of Khakassia in south-central Siberia, 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_69e0c467e1f48190af2650b19175abc4 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef6c0956e0819093b4794418efe052 completed April 27, 2026, 2 p.m.
Created at: April 16, 2026, 6:36 p.m.