Triple

T21477952
Position Surface form Disambiguated ID Type / Status
Subject Kashmir division E529911 entity
Predicate hasTown P847 FINISHED
Object Kulgam NE NERFINISHED

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: Kulgam | Statement: [Kashmir division, hasTown, Kulgam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kulgam
Context triple: [Kashmir division, hasTown, Kulgam]
  • A. Kulgam district chosen
    Kulgam district is an administrative district in the Union Territory of Jammu and Kashmir in northern India, known for its scenic landscapes and agricultural economy.
  • B. Budgam
    Budgam is a town in the central part of the Kashmir region of India, serving as the administrative headquarters of Budgam district.
  • C. 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.
  • D. 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.
  • E. Swabi
    Swabi is a city in northern Pakistan known as an agricultural and commercial center in the Khyber Pakhtunkhwa province.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c459acb481909bb6ee452a0045c7 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e9ea1951fc8190910f634327aa5c3f completed April 23, 2026, 9:44 a.m.
Created at: April 16, 2026, 6:20 p.m.