Triple

T1916063
Position Surface form Disambiguated ID Type / Status
Subject Bundelkhand E40019 entity
Predicate hasCity P316 FINISHED
Object Jhansi E22224 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: Jhansi | Statement: [Bundelkhand, hasCity, Jhansi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jhansi
Context triple: [Bundelkhand, hasCity, Jhansi]
  • A. Jhansi chosen
    Jhansi is a historic city in northern India, renowned for its strategic fort and its central role in the 1857 uprising against British colonial rule.
  • B. Jabalpur
    Jabalpur is a major city in the central Indian state of Madhya Pradesh, known for its industrial base, educational institutions, and nearby marble rock formations along the Narmada River.
  • C. Gwalior
    Gwalior is a historic city in the Indian state of Madhya Pradesh, renowned for its hilltop fort, rich royal heritage, and cultural significance.
  • D. Chanderi
    Chanderi is a historic town in central India renowned for its medieval architecture and its traditional handwoven Chanderi silk and cotton textiles.
  • E. Budaun
    Budaun is a historic city in the Rohilkhand region of Uttar Pradesh, India, known for its medieval heritage and cultural significance.
  • 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_69af174f97248190817a64dfbf98c360 completed March 9, 2026, 6:54 p.m.
Created at: March 4, 2026, 7:35 p.m.