Triple

T9669549
Position Surface form Disambiguated ID Type / Status
Subject Tuvan E233990 entity
Predicate hasDialects P4251 FINISHED
Object Southeastern Tuvan 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: Southeastern Tuvan | Statement: [Tuvan, hasDialects, Southeastern Tuvan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Southeastern Tuvan
Context triple: [Tuvan, hasDialects, Southeastern Tuvan]
  • 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. Lower Tanana language
    The Lower Tanana language is an endangered Northern Athabaskan language traditionally spoken by the Tanana people in the interior region of Alaska.
  • C. Tsakhur language
    The Tsakhur language is a Northeast Caucasian language spoken primarily by the Tsakhur people in parts of Azerbaijan and Dagestan.
  • D. Altai language
    The Altai language is a Turkic language spoken primarily in Russia’s Altai Republic and surrounding regions by the indigenous Altai people.
  • E. Khakas language
    Khakas language is a Turkic language spoken primarily by the Khakas people in the Republic of Khakassia in south-central Siberia, 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_69ca848f55e48190b3f67252571c3d45 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9c3d5b3481908c8c66a3528875aa completed April 1, 2026, 10:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69d19f70597c81909d461b3d935b02a5 completed April 4, 2026, 11:32 p.m.
Created at: March 30, 2026, 8:15 p.m.