Triple

T10149371
Position Surface form Disambiguated ID Type / Status
Subject Dungarpur State E232589 entity
Predicate borderedBy P224 FINISHED
Object Banswara State 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 State | Statement: [Dungarpur State, borderedBy, Banswara State]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Banswara State
Context triple: [Dungarpur State, borderedBy, Banswara State]
  • A. 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.
  • B. Sirohi State
    Sirohi State was a princely state in western India, ruled by Rajput chiefs and later integrated into the Indian Union after independence.
  • C. Dungarpur State
    Dungarpur State was a princely state in western India, historically ruled by Rajput chiefs and later integrated into the modern state of Rajasthan.
  • D. Narsinghgarh State
    Narsinghgarh State was a former princely state in central India, historically ruled by local royalty under British suzerainty.
  • E. Jhabua State
    Jhabua State was a former princely state in western India, located in what is now Madhya Pradesh and historically ruled by Rajput chiefs under British suzerainty.
  • 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_69ca84885e48819088a31b127cf44904 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cdec03e80c81909c813dae91c56272 completed April 2, 2026, 4:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69d3009992388190ab2a4aee23d0e004 completed April 6, 2026, 12:38 a.m.
Created at: March 30, 2026, 9:08 p.m.