Triple

T636531
Position Surface form Disambiguated ID Type / Status
Subject Turkmen language E16633 entity
Predicate hasDialect P4251 FINISHED
Object Teke dialect E79932 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: Teke dialect | Statement: [Turkmen language, hasDialect, Teke dialect]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Teke dialect
Context triple: [Turkmen language, hasDialect, Teke dialect]
  • A. Teke dialect chosen
    The Teke dialect is a major variety of Turkmen that serves as the basis for the language’s modern standard form.
  • B. Doabi dialect
    The Doabi dialect is a regional variety of Punjabi traditionally spoken in the Doaba region of the Indian state of Punjab, between the Beas and Sutlej rivers.
  • C. Wipukpa dialect
    The Wipukpa dialect is a regional variety of the Yavapai language traditionally spoken by a subgroup of the Yavapai people in central Arizona.
  • D. Malwai dialect
    The Malwai dialect is a regional variety of Punjabi primarily spoken in the Malwa region of the Indian state of Punjab.
  • E. Nupe language
    The Nupe language is a Niger-Congo language spoken primarily by the Nupe people in central Nigeria, especially in the Middle Belt region.
  • 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_69a4936be1c88190af56540324b57da7 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a49ee7fdbc8190858e42bb1bfdb3ff completed March 1, 2026, 8:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69a5778daa0881908311823d8db543ae completed March 2, 2026, 11:42 a.m.
Created at: March 1, 2026, 7:35 p.m.