Triple

T11740117
Position Surface form Disambiguated ID Type / Status
Subject Mewar region E279129 entity
Predicate hasMajorCity P316 FINISHED
Object Banswara E228625 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: Banswara | Statement: [Mewar region, hasMajorCity, Banswara]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Banswara
Context triple: [Mewar region, hasMajorCity, Banswara]
  • A. Sirohi
    Sirohi is a town in the Indian state of Rajasthan known for its historical significance and role as the former seat of a princely state.
  • B. Jalore
    Jalore is a historic town and district headquarters in the Indian state of Rajasthan, known for its ancient fort and role in the Marwar region’s history.
  • C. Banswara State chosen
    Banswara State was a princely state in what is now Rajasthan, India, historically ruled by Rajput chiefs and later integrated into the Indian Union after independence.
  • D. 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.
  • E. Jhalawar
    Jhalawar is a town and administrative district headquarters in southeastern Rajasthan, India, known for its historic forts, temples, and rich Hadoti cultural heritage.
  • 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_69d6aaffec6881908bead509e8621742 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a4f025f88190a39280806c9d7c33 completed April 10, 2026, 7:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69f280c4d8f4819094f3ebf67f4584a5 completed April 29, 2026, 10:05 p.m.
Created at: April 8, 2026, 9:41 p.m.