Triple

T1916069
Position Surface form Disambiguated ID Type / Status
Subject Bundelkhand E40019 entity
Predicate hasCity P316 FINISHED
Object Mahoba E216380 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: Mahoba | Statement: [Bundelkhand, hasCity, Mahoba]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mahoba
Context triple: [Bundelkhand, hasCity, Mahoba]
  • A. Mahoba chosen
    Mahoba is a historic town in Uttar Pradesh, India, renowned for its role as a prominent center of power and culture in the Bundelkhand region, especially under the Chandela rulers.
  • B. Pandua
    Pandua is a historic city in present-day West Bengal, India, that served as an important political and cultural center during the medieval Bengal Sultanate.
  • C. Kadamtala
    Kadamtala is a small settlement located on Middle Andaman Island in the Andaman and Nicobar Islands of India.
  • D. Parchal
    Parchal is a town in Portugal’s Algarve region, situated near the Arade River opposite Portimão and known historically for its fishing and canning industries.
  • E. Mahodara
    Mahodara is a revered form of the Hindu deity Ganesha, particularly associated with prosperity, generosity, and the fulfillment of devotees’ wishes.
  • 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_69a8864298748190a2f2fd34f7ef8d77 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb1e517e8819086e4bf5a305aeb25 completed March 7, 2026, 5:04 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae0310c2e08190aab7443cdfcd072a completed March 8, 2026, 11:15 p.m.
Created at: March 4, 2026, 7:35 p.m.