Triple

T11971770
Position Surface form Disambiguated ID Type / Status
Subject Hushe Valley E284936 entity
Predicate hasSettlement P1068 FINISHED
Object Hushe E923200 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: Hushe | Statement: [Hushe Valley, hasSettlement, Hushe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hushe
Context triple: [Hushe Valley, hasSettlement, Hushe]
  • A. Hushe chosen
    Hushe is a remote village in Pakistan’s Karakoram region that serves as a key gateway for trekkers and climbers heading toward major peaks and glaciers.
  • B. Kuhdasht
    Kuhdasht is a city in western Iran known as an agricultural and regional center within Lorestan Province.
  • C. Taleqan
    Taleqan is a small mountainous city in northern Iran known for its cool climate, natural landscapes, and traditional rural architecture.
  • D. Makhshirin
    Makhshirin is a tractate of the Mishnah in Seder Tohorot that deals with the liquids and conditions that render foods susceptible to ritual impurity.
  • E. Hormuzd
    Hormuzd is a masculine given name most notably borne by Hormuzd Rassam, a 19th-century Assyriologist and archaeologist known for his discoveries of ancient Mesopotamian artifacts.
  • 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_69d6ab2eaeb881909f7914758f859413 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d9037d32e88190b1509285dc907d29 completed April 10, 2026, 2:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69f4597cf818819089b0d897c236b87b completed May 1, 2026, 7:42 a.m.
Created at: April 8, 2026, 9:46 p.m.