Triple

T21201563
Position Surface form Disambiguated ID Type / Status
Subject Roshani language E522465 entity
Predicate contactWith P19362 FINISHED
Object Tajik language NE NERFINISHED

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: Tajik language | Statement: [Roshani language, contactWith, Tajik language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tajik language
Context triple: [Roshani language, contactWith, Tajik language]
  • A. Tajik language chosen
    The Tajik language is a variety of Persian spoken primarily in Tajikistan and written in the Cyrillic script.
  • B. Judeo-Tajik
    Judeo-Tajik is a Jewish ethnolect of the Tajik (Persian) language historically spoken by Central Asian Bukharan Jews, written in Hebrew script and enriched with Hebrew and Aramaic loanwords.
  • C. Karakalpak language
    The Karakalpak language is a Turkic language spoken primarily by the Karakalpak people in Karakalpakstan, an autonomous republic within Uzbekistan.
  • D. Turkmen language
    The Turkmen language is a Turkic language spoken primarily in Turkmenistan and surrounding regions, closely related to Turkish and other Oghuz languages.
  • E. Khinalug language
    The Khinalug language is a highly endangered Northeast Caucasian language spoken by the Khinalug people in a single mountain village in northern Azerbaijan.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b5112d8881909510b2dcdc93106d completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e73431973c81908c8682d7808a9d13 completed April 21, 2026, 8:24 a.m.
Created at: April 16, 2026, 3:18 p.m.