Triple

T5684226
Position Surface form Disambiguated ID Type / Status
Subject Nimar E125271 entity
Predicate hasMajorTown P316 FINISHED
Object Maheshwar E269512 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: Maheshwar | Statement: [Nimar, hasMajorTown, Maheshwar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maheshwar
Context triple: [Nimar, hasMajorTown, 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. Chitrakoot
    Chitrakoot is a revered pilgrimage town in India celebrated in the Ramayana as a key place of exile and spiritual refuge for Lord Rama.
  • C. Bageshwar
    Bageshwar is a town and district headquarters in the Kumaon region of Uttarakhand, India, known for its religious significance and scenic Himalayan surroundings.
  • D. Sangameshwar
    Sangameshwar is a town in Maharashtra, India, historically notable as the site where Maratha ruler Sambhaji was captured by Mughal forces.
  • E. Jagadhri
    Jagadhri is a city in the Indian state of Haryana, known historically for its metal and brass industries and forming a twin city with Yamunanagar.
  • 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_69c0082a884c8190a79001bae658941f completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c023b8efc4819085675d0d3dfb2a54 completed March 22, 2026, 5:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69c097def5dc819095b881d687d5447d completed March 23, 2026, 1:31 a.m.
Created at: March 22, 2026, 3:44 p.m.