Triple

T15186695
Position Surface form Disambiguated ID Type / Status
Subject Kuno National Park E362893 entity
Predicate nearestCity P350 FINISHED
Object Sheopur E158564 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: Sheopur | Statement: [Kuno National Park, nearestCity, Sheopur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sheopur
Context triple: [Kuno National Park, nearestCity, Sheopur]
  • A. Sheopur chosen
    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.
  • B. Daryapur
    Daryapur is a town in the Amravati district of Maharashtra, India, known for its agricultural economy and regional market activities.
  • C. Mahipalpur
    Mahipalpur is an urban village and commercial area in Delhi, India, located near Indira Gandhi International Airport and known for its hotels, transport hubs, and proximity to major highways.
  • D. Sikandarpur
    Sikandarpur is a metro station in the Delhi Metro network that serves the Gurugram area and provides an interchange with the Rapid Metro system.
  • E. Jaisinghpur
    Jaisinghpur is a town located in the Sultanpur district of the Indian state of Uttar Pradesh.
  • 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_69d85a09a39c81908759f23268e2d408 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0067995fc8190b048f15086bd42f0 completed April 15, 2026, 9:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69ff0b35c5488190a22195578c6da855 completed May 9, 2026, 10:23 a.m.
Created at: April 10, 2026, 3:09 a.m.