Triple

T4794704
Position Surface form Disambiguated ID Type / Status
Subject Sakha people E106683 entity
Predicate nativeName P15 FINISHED
Object Саха E434976 NE FINISHED

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: Саха | Statement: [Sakha people, nativeName, Саха]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Саха
Context triple: [Sakha people, nativeName, Саха]
  • A. Yakut
    Yakut is a Turkic language spoken primarily in the Sakha Republic (Yakutia) in northeastern Siberia, Russia.
  • B. Sakha chosen
    Sakha is a Turkic language spoken primarily in the Sakha Republic (Yakutia) in northeastern Siberia, Russia.
  • C. Koryak
    The Koryak are an Indigenous people of northeastern Siberia, traditionally semi-nomadic reindeer herders and coastal hunters with a distinct Chukotko-Kamchatkan language and culture.
  • D. Nanai
    The Nanai are an indigenous Tungusic people of the Russian Far East and northeastern China, traditionally known for fishing, hunting, and a river-based way of life along the Amur and Ussuri rivers.
  • E. Transbaikal
    Transbaikal is a historical and geographical region of southeastern Siberia in Russia, stretching east of Lake Baikal toward the borders with Mongolia and China.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69bd43f591c881909e5a532388b0f3f3 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd66088d588190839acfbac6e1c3dd completed March 20, 2026, 3:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69be4d9a76c08190bd19fcef378cd640 completed March 21, 2026, 7:49 a.m.
Created at: March 20, 2026, 1:22 p.m.