Triple

T9561572
Position Surface form Disambiguated ID Type / Status
Subject Shughni E230685 entity
Predicate hasAlternativeName P39 FINISHED
Object Shughnani 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: Shughnani | Statement: [Shughni, hasAlternativeName, Shughnani]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shughnani
Context triple: [Shughni, hasAlternativeName, Shughnani]
  • 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. Shushary
    Shushary is a municipal settlement in the southern part of Saint Petersburg, Russia, known for its residential areas and industrial facilities.
  • C. Barshaini
    Barshaini is a small Himalayan village in Himachal Pradesh, India, that serves as a popular base and trailhead for treks into the Parvati Valley and surrounding high-altitude landscapes.
  • D. 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.
  • E. Sangisari
    Sangisari is an Iranian language spoken by the Sangisari people in the Semnan Province of north-central Iran.
  • 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_69ca847e53a88190a60eed7e02257f10 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd994d31e08190b139f5ad10d8ea31 completed April 1, 2026, 10:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69d17900ae2c819087a83f6c74a59afc completed April 4, 2026, 8:48 p.m.
Created at: March 30, 2026, 8:03 p.m.