Triple

T9542460
Position Surface form Disambiguated ID Type / Status
Subject Ersari E230190 entity
Predicate languageDialect P1762 FINISHED
Object Ersari dialect of Turkmen E16633 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: Ersari dialect of Turkmen | Statement: [Ersari, languageDialect, Ersari dialect of Turkmen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ersari dialect of Turkmen
Context triple: [Ersari, languageDialect, Ersari dialect of Turkmen]
  • A. Turkmen language chosen
    The Turkmen language is a Turkic language spoken primarily in Turkmenistan and surrounding regions, closely related to Turkish and other Oghuz languages.
  • B. Saryk dialect
    The Saryk dialect is a regional variety of the Turkmen language traditionally spoken by the Saryk Turkmen people of Central Asia.
  • C. Khunzakh dialect
    The Khunzakh dialect is a regional variety of the Avar language spoken in and around the village of Khunzakh in Dagestan, Russia.
  • D. Buynaksk dialect
    The Buynaksk dialect is a regional variety of the Kumyk language spoken around the city of Buynaksk in Dagestan, Russia.
  • E. Turu dialect
    Turu dialect is a regional variety of the Berom language spoken by Berom communities in parts of central Nigeria.
  • 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_69ca847c70b8819088a0a0bad64a50d6 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd98e9be048190bf1f01884ff7c362 completed April 1, 2026, 10:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69d14c6538b08190a9f81304214a876d completed April 4, 2026, 5:37 p.m.
Created at: March 30, 2026, 8:01 p.m.