Triple

T3042469
Position Surface form Disambiguated ID Type / Status
Subject Salyr dialect E83161 entity
Predicate statusWithinLanguage P7163 FINISHED
Object non-standard variety of Turkmen LITERAL 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: non-standard variety of Turkmen | Statement: [Salyr dialect, statusWithinLanguage, non-standard variety of Turkmen]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: statusWithinLanguage
Context triple: [Salyr dialect, statusWithinLanguage, non-standard variety of Turkmen]
  • A. hasLanguageStatus
    Indicates that an entity has a particular status or condition regarding its language use, recognition, or classification.
  • B. officialLanguageStatusSharedWith
    Indicates that two entities share at least one official language in common.
  • C. ethnicLanguageStatus
    Indicates the status or role of a language in relation to a particular ethnic group (e.g., primary, secondary, heritage, or minority language).
  • D. languageFamilyStatus
    Indicates the classification or recognition status of a language within a particular language family (e.g., primary, branch, extinct, or disputed).
  • E. sociolinguisticStatus chosen
    Indicates the social and cultural standing or prestige associated with a language variety or linguistic feature within a particular community or context.
  • F. None of above.

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_69ad8b2298908190a7cb4e9bdbf064d0 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9b5d2a308190b4ce20efcae9b761 completed March 8, 2026, 3:53 p.m.
PD Predicate disambiguation batch_69ad961fc62c819087c4c3a44b00847d completed March 8, 2026, 3:30 p.m.
Created at: March 8, 2026, 3:01 p.m.