Triple

T5361604
Position Surface form Disambiguated ID Type / Status
Subject Northeastern Turkic E103033 entity
Predicate hasMember P10 FINISHED
Object Tuvan language E233990 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: Tuvan language | Statement: [Northeastern Turkic, hasMember, Tuvan language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tuvan language
Context triple: [Northeastern Turkic, hasMember, Tuvan language]
  • A. Tuvan chosen
    Tuvan is a Turkic language spoken primarily in the Tuva Republic of Russia, known for its rich oral traditions and association with Tuvan throat singing.
  • B. Sakha language
    The Sakha language is a Turkic language spoken primarily by the Sakha (Yakut) people in northeastern Siberia, where it serves as a major regional and cultural language.
  • C. Nenets language
    The Nenets language is a Uralic Samoyedic language spoken by the Nenets people of northern Arctic Russia.
  • D. Enets language
    Enets language is a critically endangered Samoyedic language of the Uralic family spoken by a small Indigenous community in northern Siberia, Russia.
  • E. Sibe language
    Sibe language is a modern Tungusic language spoken primarily by the Sibe people in Xinjiang, China, and is closely related to Manchu.
  • 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_69bd43daa3e4819090b59d127db70e57 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd865a0bb081909579cfe7c7974075 completed March 20, 2026, 5:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf21ef7acc8190aa7ff990a04ff09c completed March 21, 2026, 10:55 p.m.
Created at: March 20, 2026, 2:02 p.m.