Triple

T15410395
Position Surface form Disambiguated ID Type / Status
Subject Ulchsky District E368573 entity
Predicate hasMinorityLanguage P2267 FINISHED
Object Ulch language 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: Ulch language | Statement: [Ulchsky District, hasMinorityLanguage, Ulch language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ulch language
Context triple: [Ulchsky District, hasMinorityLanguage, Ulch language]
  • 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. Udege language
    The Udege language is a critically endangered Tungusic language spoken by the Udege people of the Russian Far East.
  • C. Chulym language
    The Chulym language is a critically endangered Turkic language spoken by a small indigenous community in Siberia, Russia.
  • D. Selkup language
    The Selkup language is a critically endangered Uralic (Samoyedic) language spoken by the indigenous Selkup people of western Siberia in Russia.
  • E. Tsakhur language
    The Tsakhur language is a Northeast Caucasian language spoken primarily by the Tsakhur people in parts of Azerbaijan and Dagestan.
  • 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_69d85a16c68c819099c1b547fbc87b32 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03ea4f13c819085d26fd32b5dca6f completed April 16, 2026, 1:43 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff1a7356548190af5651ab0bc03ab9 completed May 9, 2026, 11:28 a.m.
Created at: April 10, 2026, 3:20 a.m.