Triple

T961725
Position Surface form Disambiguated ID Type / Status
Subject Central India E20748 entity
Predicate containsCity P294 FINISHED
Object Shivpuri E133914 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: Shivpuri | Statement: [Central India, containsCity, Shivpuri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shivpuri
Context triple: [Central India, containsCity, Shivpuri]
  • A. Shivpuri chosen
    Shivpuri is a historic town and former princely state in central India, known for its forests, wildlife sanctuaries, and royal palaces.
  • B. Bhind
    Bhind is a city in the northern part of the Indian state of Madhya Pradesh, known as an administrative and commercial center of the region.
  • C. Jagdishpur
    Jagdishpur is a town in the Bhojpur district of Bihar, India, historically known as the ancestral estate of the 19th-century freedom fighter Kunwar Singh.
  • D. Sheopur
    Sheopur is a town and district headquarters in the northern part of the Indian state of Madhya Pradesh, known for its proximity to the Kuno National Park and its largely rural, agrarian surroundings.
  • E. Alirajpur
    Alirajpur is a town and district headquarters in western Madhya Pradesh, India, known for its predominantly tribal population and vibrant indigenous culture.
  • 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_69a493b21f2881908132dcf45dcd2f36 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b415ac688190bbcef455935a3116 completed March 1, 2026, 9:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad08995af88190930a952bd32cd918 completed March 8, 2026, 5:26 a.m.
Created at: March 1, 2026, 7:40 p.m.