Triple

T14145992
Position Surface form Disambiguated ID Type / Status
Subject Battle of Chanderi E350550 entity
Predicate location P40 FINISHED
Object Chanderi E171083 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: Chanderi | Statement: [Battle of Chanderi, location, Chanderi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chanderi
Context triple: [Battle of Chanderi, location, Chanderi]
  • A. Chanderi chosen
    Chanderi is a historic town in central India renowned for its medieval architecture and its traditional handwoven Chanderi silk and cotton textiles.
  • B. Jhansi
    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.
  • C. Chittorgarh
    Chittorgarh is a historic city in Rajasthan, India, renowned for its massive hilltop fort, tales of Rajput valor, and rich cultural traditions.
  • D. Gwalior
    Gwalior is a historic city in the Indian state of Madhya Pradesh, renowned for its hilltop fort, rich royal heritage, and cultural significance.
  • E. Orchha
    Orchha is a historic town in central India renowned for its medieval palaces, temples, and riverside cenotaphs built by the Bundela Rajput rulers.
  • 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_69d827865f608190b311820428ae027b completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de612266248190a8591b646fe30ae6 completed April 14, 2026, 3:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd6d77e8dc8190b90f3505960e549e completed May 8, 2026, 4:58 a.m.
Created at: April 10, 2026, 12:53 a.m.