Triple

T22241123
Position Surface form Disambiguated ID Type / Status
Subject Bartangi E549724 entity
Predicate neighboringLanguages P16383 FINISHED
Object Shughni 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: Shughni | Statement: [Bartangi, neighboringLanguages, Shughni]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shughni
Context triple: [Bartangi, neighboringLanguages, Shughni]
  • A. Shughni chosen
    Shughni is an Eastern Iranian language spoken primarily in the Badakhshan region of Tajikistan and Afghanistan, known for its use among the Shughni people in the Pamir Mountains.
  • B. Khashuri
    Khashuri is a town in central Georgia that serves as an important regional transport hub and gateway between eastern and western parts of the country.
  • C. Barya
    Barya is an alternative name for the Nara people, an ethnic group primarily inhabiting parts of Eritrea.
  • D. Ghudushauri
    Ghudushauri is a Georgian family or clan, notably associated with Irakli Ghudushauri-Shiolashvili.
  • E. Shavsheti
    Shavsheti is a historical region or locality within the medieval Georgian cultural-geographical area of Tao-Klarjeti.
  • 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_69e11e41d9408190bd770cf282e22753 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f132140ed481909ab0d4022756a4ba completed April 28, 2026, 10:17 p.m.
Created at: April 16, 2026, 8:38 p.m.