Triple

T21975032
Position Surface form Disambiguated ID Type / Status
Subject Mangla Lake E542682 entity
Predicate locatedNear P294 FINISHED
Object Mangla 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: Mangla | Statement: [Mangla Lake, locatedNear, Mangla]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mangla
Context triple: [Mangla Lake, locatedNear, Mangla]
  • A. Mangla chosen
    Mangla is a town in Pakistan best known for the nearby Mangla Dam, one of the largest earth-fill dams in the world, built on the Jhelum River.
  • B. Sangla
    Sangla is a picturesque town in Himachal Pradesh’s Kinnaur district, known for its scenic Himalayan valley, apple orchards, and traditional Kinnauri culture.
  • C. Bhavra
    Bhavra is a village in present-day Madhya Pradesh, India, historically notable as the birthplace of Indian revolutionary freedom fighter Chandrasekhar Azad.
  • D. Bhera River
    The Bhera River is a significant tributary watercourse that feeds into eastern India’s Damodar River system.
  • E. Chamba River
    The Chamba River is a lesser-known tributary stream that feeds into the Lower Tunguska River in the Siberian region of Russia.
  • 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_69e0c48070988190909db97667b9a0ac completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f12487a1a88190abb8a51fcd533b6a completed April 28, 2026, 9:20 p.m.
Created at: April 16, 2026, 8:03 p.m.