Triple

T23236343
Position Surface form Disambiguated ID Type / Status
Subject Koryak Autonomous Okrug E581306 entity
Predicate languageUsed P238 FINISHED
Object Koryak 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: Koryak language | Statement: [Koryak Autonomous Okrug, languageUsed, Koryak language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Koryak language
Context triple: [Koryak Autonomous Okrug, languageUsed, Koryak language]
  • A. Koryak language chosen
    Koryak language is a Chukotko-Kamchatkan language spoken by the Indigenous Koryak people of northeastern Siberia in Russia.
  • B. Chukchi language
    The Chukchi language is a Chukotko-Kamchatkan language spoken by the Indigenous Chukchi people of northeastern Siberia, Russia.
  • C. 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.
  • 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. Nanai language
    Nanai language is a critically endangered Tungusic language spoken by the Nanai people of the Russian Far East and northeastern China.
  • 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_69e2460556f88190be1744a84a84173f completed April 17, 2026, 2:39 p.m.
NER Named-entity recognition batch_69f192e98dec8190a23385600bed9ae0 completed April 29, 2026, 5:11 a.m.
Created at: April 17, 2026, 4:09 p.m.