Triple

T13804167
Position Surface form Disambiguated ID Type / Status
Subject Nagarhole National Park E331717 entity
Predicate nearestTown P350 FINISHED
Object Hunsur E1032185 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: Hunsur | Statement: [Nagarhole National Park, nearestTown, Hunsur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hunsur
Context triple: [Nagarhole National Park, nearestTown, Hunsur]
  • A. Hunsur chosen
    Hunsur is a town in the Indian state of Karnataka known for its agricultural economy and proximity to forested and wildlife-rich areas.
  • B. Kundapur Vaman
    Kundapur Vaman is the full given name of K. V. Kamath, a prominent Indian banker and former president of the New Development Bank and ex-CEO of ICICI Bank.
  • C. Nandighosa
    Nandighosa is the grand, elaborately decorated main chariot used to carry Lord Jagannath during the annual Rath Yatra festival in Puri, India.
  • D. Shivaram
    Shivaram is the given name of Shivaram Rajguru, an Indian revolutionary best known for his role in the Indian independence movement alongside Bhagat Singh.
  • E. Bhimsagar
    Bhimsagar is a notable historical site in Rajasthan, India, recognized for its heritage significance within the Jhalawar region.
  • 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_69d81c59f8808190a851bc56afdc55e9 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de026c36108190a7436034a730a261 completed April 14, 2026, 9:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7b08bd7c48190bcdf110ccd27c003 completed May 3, 2026, 8:31 p.m.
Created at: April 9, 2026, 10:12 p.m.