Triple

T20484774
Position Surface form Disambiguated ID Type / Status
Subject Narmada Valley E502559 entity
Predicate contains P35 FINISHED
Object Maheshwar 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: Maheshwar | Statement: [Narmada Valley, contains, Maheshwar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maheshwar
Context triple: [Narmada Valley, contains, Maheshwar]
  • A. Maheshwar chosen
    Maheshwar is a historic temple town on the banks of the Narmada River in Madhya Pradesh, India, renowned for its ghats, fort, and traditional handwoven Maheshwari sarees.
  • B. Gopeshwar
    Gopeshwar is a town in the Indian state of Uttarakhand known as a local commercial and cultural center in the Garhwal Himalayas.
  • C. Bhuleshwar
    Bhuleshwar is a densely populated, historic market and residential area in South Mumbai known for its traditional temples, jewelry and textile shops, and vibrant street life.
  • D. Shankheshwar
    Shankheshwar is a village in Gujarat, India, known primarily as a significant Jain pilgrimage center dedicated to Lord Parshvanath.
  • E. Ramdurg
    Ramdurg is a town in the Indian state of Karnataka, known for its historical temples and its location within the Belagavi region.
  • 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_69e0b4af32848190aea80682b44d5d6e completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e69b59ae2c8190bfa26a3f1e59b8d1 completed April 20, 2026, 9:32 p.m.
Created at: April 16, 2026, 11:34 a.m.