Triple

T10933755
Position Surface form Disambiguated ID Type / Status
Subject Rumbur Valley E258274 entity
Predicate hasLanguage P15 FINISHED
Object Kalasha-mun E722614 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: Kalasha-mun | Statement: [Rumbur Valley, hasLanguage, Kalasha-mun]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kalasha-mun
Context triple: [Rumbur Valley, hasLanguage, Kalasha-mun]
  • A. Kalasha chosen
    Kalasha is an endangered Indo-Aryan language spoken by the Kalash people in the remote valleys of northern Pakistan.
  • B. Nuristani Kalasha
    Nuristani Kalasha is an Indo-Iranian language of the Nuristani branch spoken in parts of eastern Afghanistan.
  • C. Shangarh
    Shangarh is a scenic Himalayan village in Himachal Pradesh, India, known for its expansive meadows, traditional wooden temples, and tranquil setting within the Great Himalayan National Park region.
  • D. Parwanoo
    Parwanoo is an industrial town in the Solan district of Himachal Pradesh, India, known for its manufacturing units and proximity to the Haryana border.
  • E. Jarung Khashor
    Jarung Khashor is the traditional Tibetan name for the Boudhanath Stupa, one of the largest and most important Buddhist stupas in Nepal and a major pilgrimage site.
  • 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_69d6aa8769b4819082bfe5e61b9017f0 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d770ae073881909720febe9f5f296a completed April 9, 2026, 9:26 a.m.
NED1 Entity disambiguation (via context triple) batch_69e2176328448190bbce6735ec97507a completed April 17, 2026, 11:20 a.m.
Created at: April 8, 2026, 9:23 p.m.