Triple

T19922629
Position Surface form Disambiguated ID Type / Status
Subject Panna district E478835 entity
Predicate headquarters P62 FINISHED
Object Panna 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: Panna | Statement: [Panna district, headquarters, Panna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Panna
Context triple: [Panna district, headquarters, Panna]
  • A. Panna chosen
    Panna is a town in central India renowned for its diamond mines and proximity to Panna National Park, a noted tiger reserve.
  • B. Pachpadra
    Pachpadra is a town in Rajasthan, India, known for its traditional salt pans and location along key transport routes in the Barmer district.
  • C. Pupri
    Pupri is a small town in the Sitamarhi district of the Indian state of Bihar, known primarily as a local commercial and administrative center for surrounding rural areas.
  • D. Chitrari
    Chitrari is an alternative name for the Khowar language, an Indo-Aryan language spoken primarily in the Chitral region of northern Pakistan.
  • E. Paddhari
    Paddhari is a town in the western Indian state of Gujarat, known as a local market hub within the Rajkot 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_69d8e521855c8190b41871700afc8d6a completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e659c6919c8190a96106532580b6b6 completed April 20, 2026, 4:52 p.m.
Created at: April 10, 2026, 1:53 p.m.