Triple

T6316780
Position Surface form Disambiguated ID Type / Status
Subject Gwalior division E141635 entity
Predicate hasMajorTown P316 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: [Gwalior division, hasMajorTown, Shivpuri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shivpuri
Context triple: [Gwalior division, hasMajorTown, 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. Sohagpur
    Sohagpur is a town in the Narmadapuram district of Madhya Pradesh, India, known as a local commercial center and access point to nearby forested and wildlife areas.
  • C. Tuljapur
    Tuljapur is a town in Maharashtra, India, renowned as a major pilgrimage center for the goddess Bhavani.
  • D. 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.
  • E. Karauli
    Karauli is a historic town and pilgrimage center in the Indian state of Rajasthan, known for its ancient temples and distinctive red sandstone architecture.
  • 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_69c008d13b8c8190be47d896eb735605 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c064c25530819080b29e0029175c00 completed March 22, 2026, 9:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69c640aa8b608190ab834e77613f5218 completed March 27, 2026, 8:32 a.m.
Created at: March 22, 2026, 4:29 p.m.