Triple

T9561574
Position Surface form Disambiguated ID Type / Status
Subject Shughni E230685 entity
Predicate hasAlternativeName P39 FINISHED
Object Shughnī 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: Shughnī | Statement: [Shughni, hasAlternativeName, Shughnī]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shughnī
Context triple: [Shughni, hasAlternativeName, Shughnī]
  • 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. Bakhah
    Bakhah is a village in Syria known as one of the few remaining communities where Western Neo-Aramaic is still actively spoken.
  • C. Mughniyeh
    Mughniyeh is a Lebanese family name most prominently associated with Imad Mughniyeh, a senior Hezbollah military commander.
  • D. Shemshak
    Shemshak is a mountain village and ski resort in the Alborz range of northern Iran, known for its steep slopes and popularity among advanced skiers.
  • E. Ghebala
    Ghebala is a town and commune located within Jijel Province in northeastern Algeria.
  • 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_69d18214e1cc8190a66582a1af26cac3 completed April 4, 2026, 9:26 p.m.
Created at: March 30, 2026, 8:03 p.m.