Triple

T12615255
Position Surface form Disambiguated ID Type / Status
Subject Nowshak E301233 entity
Predicate hasAlternativeName P39 FINISHED
Object Noshak E62190 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: Noshak | Statement: [Nowshak, hasAlternativeName, Noshak]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Noshak
Context triple: [Nowshak, hasAlternativeName, Noshak]
  • A. Noshaq chosen
    Noshaq is a prominent mountain in the Hindu Kush range, straddling the Afghanistan–Pakistan border and known as one of the region’s highest and most challenging peaks.
  • B. Hushe
    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.
  • C. 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.
  • D. Nokha
    Nokha is a town in the Indian state of Rajasthan, known as a commercial and agricultural center within the Bikaner region.
  • E. Kuhdasht
    Kuhdasht is a city in western Iran known as an agricultural and regional center within Lorestan Province.
  • 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_69d7bdeaf49c8190b13800111fa77ea3 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d960c4f5b48190af76414ef678ba7c completed April 10, 2026, 8:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69f67c6f8e9881908f350aa3cefef269 completed May 2, 2026, 10:36 p.m.
Created at: April 9, 2026, 5:12 p.m.