Triple

T8531472
Position Surface form Disambiguated ID Type / Status
Subject Hulunbuir E201959 entity
Predicate languageUsed P238 FINISHED
Object Evenki language E302341 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: Evenki language | Statement: [Hulunbuir, languageUsed, Evenki language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Evenki language
Context triple: [Hulunbuir, languageUsed, Evenki language]
  • A. Evenki language chosen
    The Evenki language is a Northern Tungusic language spoken by the Evenki people across Siberia, northeastern China, and Mongolia.
  • B. Enets language
    Enets language is a critically endangered Samoyedic language of the Uralic family spoken by a small Indigenous community in northern Siberia, Russia.
  • C. Votic language
    The Votic language is a nearly extinct Uralic language traditionally spoken by the Votes in Ingria, near the Gulf of Finland in northwestern Russia.
  • D. Nenets language
    The Nenets language is a Uralic Samoyedic language spoken by the Nenets people of northern Arctic Russia.
  • E. Khanty language
    The Khanty language is a Uralic language spoken by the Khanty people of western Siberia, closely related to Mansi and traditionally used in the Khanty-Mansi Autonomous Okrug of Russia.
  • 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_69ca83228b24819085d22e7dc99f5d94 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe676e2ac8190b65a3d2a935776fd completed March 31, 2026, 3:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69ce6d68d14c81908bde8ca0113f9503 completed April 2, 2026, 1:21 p.m.
Created at: March 30, 2026, 6:17 p.m.