Triple

T19599347
Position Surface form Disambiguated ID Type / Status
Subject Olonkho epic E470426 entity
Predicate hasLanguage P15 FINISHED
Object Yakut 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: Yakut language | Statement: [Olonkho epic, hasLanguage, Yakut language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yakut language
Context triple: [Olonkho epic, hasLanguage, Yakut language]
  • A. Khakas language
    Khakas language is a Turkic language spoken primarily by the Khakas people in the Republic of Khakassia in south-central Siberia, Russia.
  • B. Yakutic languages
    The Yakutic languages are a small branch of the Turkic language family spoken primarily in northeastern Siberia, most notably including the Sakha (Yakut) language.
  • C. Koryak language
    Koryak language is a Chukotko-Kamchatkan language spoken by the Indigenous Koryak people of northeastern Siberia in Russia.
  • D. Nivkh language
    The Nivkh language is an isolate spoken by the indigenous Nivkh people of Russia’s Far East, primarily on Sakhalin Island and along the lower Amur River.
  • E. Sakha language chosen
    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.
  • 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_69d8e510024481908415c0d616fa6186 completed April 10, 2026, 11:54 a.m.
NER Named-entity recognition batch_69e6407d46188190b9818665b2a698a5 completed April 20, 2026, 3:04 p.m.
Created at: April 10, 2026, 1:43 p.m.