Triple

T6734886
Position Surface form Disambiguated ID Type / Status
Subject Orchha E153727 entity
Predicate nearbyCity P350 FINISHED
Object Tikamgarh E143463 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: Tikamgarh | Statement: [Orchha, nearbyCity, Tikamgarh]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tikamgarh
Context triple: [Orchha, nearbyCity, Tikamgarh]
  • A. Tikamgarh chosen
    Tikamgarh is a town and administrative center in central India, known for its historical forts and temples in the state of Madhya Pradesh.
  • B. Garha-Mandla
    Garha-Mandla was a prominent medieval Gond kingdom in central India, known for its regional power and tribal dynastic rule before its eventual incorporation into larger empires.
  • C. Pratapgarh
    Pratapgarh is a town in the Indian state of Rajasthan known for its historical association with the Mewar region and its distinctive tribal culture and handicrafts.
  • D. Anuppur
    Anuppur is a town and administrative district headquarters in the central Indian state of Madhya Pradesh, known for its proximity to coal mining areas and natural attractions.
  • 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_69c6880bdd68819097de8b6099992682 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d16ecbe08190b019d547f631a725 completed March 27, 2026, 6:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69c72f86e9848190958e8f7a195fd20b completed March 28, 2026, 1:31 a.m.
Created at: March 27, 2026, 2:09 p.m.