Triple

T14933986
Position Surface form Disambiguated ID Type / Status
Subject Ishkashimi E372341 entity
Predicate closelyRelatedTo P37 FINISHED
Object Shughni E230685 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: Shughni | Statement: [Ishkashimi, closelyRelatedTo, Shughni]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shughni
Context triple: [Ishkashimi, closelyRelatedTo, 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. Shushary
    Shushary is a municipal settlement in the southern part of Saint Petersburg, Russia, known for its residential areas and industrial facilities.
  • E. Tayshet
    Tayshet is a town in Irkutsk Oblast, Russia, known as a major railway junction in Siberia.
  • 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_69d85cc9da0c81908d583ca3f63a3908 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded646a0808190ba5c0c91bde011c5 completed April 15, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe7e8c8d188190b027f14256b0ce01 completed May 9, 2026, 12:23 a.m.
Created at: April 10, 2026, 2:37 a.m.