Triple

T19432518
Position Surface form Disambiguated ID Type / Status
Subject Chukchee E486150 entity
Predicate language P15 FINISHED
Object Chukchi 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: Chukchi language | Statement: [Chukchee, language, Chukchi language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chukchi language
Context triple: [Chukchee, language, Chukchi language]
  • A. Chukchi language chosen
    The Chukchi language is a Chukotko-Kamchatkan language spoken by the Indigenous Chukchi people of northeastern Siberia, Russia.
  • B. Koryak language
    Koryak language is a Chukotko-Kamchatkan language spoken by the Indigenous Koryak people of northeastern Siberia in Russia.
  • C. Aleut language
    The Aleut language is an Indigenous Eskimo–Aleut language traditionally spoken by the Aleut people of the Aleutian Islands in Alaska and parts of Russia, now considered endangered.
  • D. 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.
  • E. 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.
  • 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_69d8e8d7ad488190a3373045029b0f3b completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6335c2d7481909a44b45d95492e02 completed April 20, 2026, 2:08 p.m.
Created at: April 10, 2026, 1:37 p.m.