Triple

T12576059
Position Surface form Disambiguated ID Type / Status
Subject Buryat language E300208 entity
Predicate hasDialect P4251 FINISHED
Object Alar-Tunka dialect
The Alar-Tunka dialect is a regional variety of the Buryat language spoken primarily in the Alar and Tunka areas of Siberia.
 E993025 NE FINISHED

How this triple was built (4 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: Alar-Tunka dialect | Statement: [Buryat language, hasDialect, Alar-Tunka dialect]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Alar-Tunka dialect
Context triple: [Buryat language, hasDialect, Alar-Tunka dialect]
  • A. Takbanuaz dialect
    The Takbanuaz dialect is a regional variety of the Bunun language spoken by an indigenous Bunun subgroup in Taiwan.
  • B. Turu dialect
    Turu dialect is a regional variety of the Berom language spoken by Berom communities in parts of central Nigeria.
  • C. Baraba dialect
    The Baraba dialect is a regional variety of the Siberian Tatar language traditionally spoken by the Baraba Tatars in southwestern Siberia.
  • D. Ersari dialect
    The Ersari dialect is a regional variety of the Turkmen language traditionally spoken by the Ersari Turkmen people, primarily in parts of Turkmenistan and neighboring regions.
  • E. Salyr dialect
    The Salyr dialect is a regional variety of the Turkmen language traditionally associated with the Salyr Turkmen tribe.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Alar-Tunka dialect
Triple: [Buryat language, hasDialect, Alar-Tunka dialect]
Generated description
The Alar-Tunka dialect is a regional variety of the Buryat language spoken primarily in the Alar and Tunka areas of Siberia.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Alar-Tunka dialect
Target entity description: The Alar-Tunka dialect is a regional variety of the Buryat language spoken primarily in the Alar and Tunka areas of Siberia.
  • A. Takbanuaz dialect
    The Takbanuaz dialect is a regional variety of the Bunun language spoken by an indigenous Bunun subgroup in Taiwan.
  • B. Turu dialect
    Turu dialect is a regional variety of the Berom language spoken by Berom communities in parts of central Nigeria.
  • C. Baraba dialect
    The Baraba dialect is a regional variety of the Siberian Tatar language traditionally spoken by the Baraba Tatars in southwestern Siberia.
  • D. Ersari dialect
    The Ersari dialect is a regional variety of the Turkmen language traditionally spoken by the Ersari Turkmen people, primarily in parts of Turkmenistan and neighboring regions.
  • E. Salyr dialect
    The Salyr dialect is a regional variety of the Turkmen language traditionally associated with the Salyr Turkmen tribe.
  • F. None of above. chosen

Provenance (5 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_69d7bde87b648190bcd0266e9efde098 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d954a629fc8190a1c3b6777aad4527 completed April 10, 2026, 7:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69f65ebab65081908a174586f0ebb16f completed May 2, 2026, 8:29 p.m.
NEDg Description generation batch_69f6617479ec819080eac67abc9bc435 completed May 2, 2026, 8:41 p.m.
NED2 Entity disambiguation (via description) batch_69f662695a348190b9911a19dfc9e779 completed May 2, 2026, 8:45 p.m.
Created at: April 9, 2026, 4:47 p.m.