Triple

T3653172
Position Surface form Disambiguated ID Type / Status
Subject Balti E77468 entity
Predicate spokenIn P2266 FINISHED
Object Baltistan E13296 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: Baltistan | Statement: [Balti, spokenIn, Baltistan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Baltistan
Context triple: [Balti, spokenIn, Baltistan]
  • A. Gilgit-Baltistan chosen
    Gilgit-Baltistan is a mountainous, strategically important region in northern Pakistan, known for its high peaks, including K2, and its location at the crossroads of South and Central Asia.
  • B. Gilgit
    Gilgit is a major town in northern Pakistan that serves as a key regional hub for trade, tourism, and access to the Karakoram mountain range.
  • C. Gilgiti Shina
    Gilgiti Shina is a regional variety of the Shina language spoken primarily in and around Gilgit in northern Pakistan.
  • D. Ladakh
    Ladakh is a high-altitude, sparsely populated region in northern India known for its rugged mountains, Buddhist culture, and strategic location bordering Tibet and the Karakoram range.
  • E. Khaplu
    Khaplu is a historic town in northern Pakistan’s Gilgit-Baltistan region, known as a gateway to the Karakoram mountains and for its traditional Balti culture and architecture.
  • 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_69ad85def5cc8190863dccf55a18bebb completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc3b805a48190a7bc230a382365d6 completed March 8, 2026, 6:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4cde0425081909ca15dba0bcc3fc4 completed March 14, 2026, 2:54 a.m.
Created at: March 8, 2026, 3:24 p.m.