Triple

T17548497
Position Surface form Disambiguated ID Type / Status
Subject Garhwal Himalaya E427391 entity
Predicate contains P35 FINISHED
Object Joshimath 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: Joshimath | Statement: [Garhwal Himalaya, contains, Joshimath]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Joshimath
Context triple: [Garhwal Himalaya, contains, Joshimath]
  • A. Joshimath chosen
    Joshimath is a Himalayan town in Uttarakhand, India, known as a gateway to pilgrimage sites like Badrinath and to trekking and skiing destinations such as Auli.
  • B. Shaktinagar
    Shaktinagar is a township in Uttar Pradesh, India, known for its power plants and associated industrial and mining activities.
  • C. Kashipur
    Kashipur is a town in the Udham Singh Nagar district of Uttarakhand, India, known as an important industrial and commercial center in the region.
  • D. Narkanda
    Narkanda is a scenic hill station in Himachal Pradesh, India, known for its apple orchards, skiing slopes, and panoramic Himalayan views.
  • E. Bilaspuri
    Bilaspuri is an Indo-Aryan language spoken primarily in the Bilaspur region of Himachal Pradesh in northern India.
  • 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_69d889df6dc081908f67dbadc03c07ee completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e454631e148190a1d46a6ecb79c71a completed April 19, 2026, 4:04 a.m.
Created at: April 10, 2026, 5:49 a.m.