Triple

T2613913
Position Surface form Disambiguated ID Type / Status
Subject Afghan E58840 entity
Predicate languageUsed P238 FINISHED
Object 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: Turkmen | Statement: [Afghan, languageUsed, Turkmen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Turkmen
Context triple: [Afghan, languageUsed, 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. Turkmens
    Turkmens are a Turkic ethnic group primarily inhabiting Turkmenistan and surrounding regions, known for their shared linguistic and cultural heritage with other Oghuz Turkic peoples.
  • C. Iraqi Turkmen
    Iraqi Turkmen are a Turkic ethnic group native to Iraq, primarily concentrated in the north of the country and culturally and linguistically related to other Oghuz Turkic peoples such as Azerbaijanis and Turks.
  • D. Kyrgyz
    Kyrgyz is a Turkic language primarily spoken in Kyrgyzstan and surrounding regions of Central Asia.
  • E. Oghuz Uzbek
    Oghuz Uzbek refers to a historical Turkic group associated with the Oghuz branch that played a key role in the ethnogenesis of the Uzbek people.
  • 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_69ab4ac444dc819099614e534dd6021f completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abd87dcfbc8190b264062002bfe4ba completed March 7, 2026, 7:49 a.m.
NED1 Entity disambiguation (via context triple) batch_69af83eb8b088190b1ea47c6d42033c5 completed March 10, 2026, 2:37 a.m.
Created at: March 6, 2026, 9:50 p.m.