Triple

T2582518
Position Surface form Disambiguated ID Type / Status
Subject Hispar Glacier E57124 entity
Predicate languageOfToponym P15 FINISHED
Object Burushaski E85247 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: Burushaski | Statement: [Hispar Glacier, languageOfToponym, Burushaski]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burushaski
Context triple: [Hispar Glacier, languageOfToponym, Burushaski]
  • A. Burushaski chosen
    Burushaski is a language isolate spoken by the Burusho people in northern Pakistan, particularly in the Hunza, Nagar, and Yasin valleys of Gilgit-Baltistan.
  • B. Brahui
    Brahui is a Dravidian language spoken primarily by the Brahui people in parts of Pakistan, Afghanistan, and Iran.
  • C. Mundari
    Mundari is an Austroasiatic Munda language of eastern India, spoken primarily by the Munda people in states such as Jharkhand, Odisha, and West Bengal.
  • D. Khowar
    Khowar is an Indo-Aryan language primarily spoken in the Chitral region of Pakistan and parts of neighboring areas, known for its rich oral tradition and distinct phonology.
  • E. Kurukh
    Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
  • 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_69ab4a4dca6481908c301f8e317396e7 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abd3c9d0548190b29743ac1d7837ff completed March 7, 2026, 7:29 a.m.
NED1 Entity disambiguation (via context triple) batch_69af657cc2b08190a9055d6da7744851 completed March 10, 2026, 12:27 a.m.
Created at: March 6, 2026, 9:49 p.m.