Triple

T12658344
Position Surface form Disambiguated ID Type / Status
Subject Ulch language E302346 entity
Predicate hasAlternativeName P39 FINISHED
Object Ulchskij jazyk E302346 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: Ulchskij jazyk | Statement: [Ulch language, hasAlternativeName, Ulchskij jazyk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ulchskij jazyk
Context triple: [Ulch language, hasAlternativeName, Ulchskij jazyk]
  • A. Ulch language chosen
    The Ulch language is a critically endangered Tungusic language spoken by the Ulch people in the Russian Far East, primarily along the lower Amur River.
  • B. Selkup language
    The Selkup language is a critically endangered Uralic (Samoyedic) language spoken by the indigenous Selkup people of western Siberia in Russia.
  • C. Udege language
    The Udege language is a critically endangered Tungusic language spoken by the Udege people of the Russian Far East.
  • D. Yukaghir
    The Yukaghir are an Indigenous people of northeastern Siberia, Russia, known for their traditional hunting and fishing lifestyle and their distinct Yukaghir languages.
  • 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 (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_69d7bded71a88190bb76e2413af9ea66 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d961636db8819099c438b24bcfd866 completed April 10, 2026, 8:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69f67c730b5c8190ae8dbb476e53729e completed May 2, 2026, 10:36 p.m.
Created at: April 9, 2026, 5:19 p.m.