Triple

T9669547
Position Surface form Disambiguated ID Type / Status
Subject Tuvan E233990 entity
Predicate hasDialects P4251 FINISHED
Object Central 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: Central Tuvan | Statement: [Tuvan, hasDialects, Central Tuvan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Central Tuvan
Context triple: [Tuvan, hasDialects, Central 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. Altai language
    The Altai language is a Turkic language spoken primarily in Russia’s Altai Republic and surrounding regions by the indigenous Altai people.
  • C. Khakas
    Khakas is a Turkic language spoken primarily by the Khakas people in the Republic of Khakassia in south-central Siberia, Russia.
  • D. Tsakhur language
    The Tsakhur language is a Northeast Caucasian language spoken primarily by the Tsakhur people in parts of Azerbaijan and Dagestan.
  • E. Tuvans
    Tuvans are a Turkic ethnic group primarily inhabiting the Tuva Republic in southern Siberia, known for their nomadic pastoral traditions and distinctive throat-singing.
  • 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_69d18a247ca48190910624dfbf0b491d completed April 4, 2026, 10:01 p.m.
Created at: March 30, 2026, 8:15 p.m.