Triple

T22427795
Position Surface form Disambiguated ID Type / Status
Subject Rajwada, Indore E554417 entity
Predicate associatedWith P37 FINISHED
Object Holkar State NE NERFINISHED

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: Holkar State | Statement: [Rajwada, Indore, associatedWith, Holkar State]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Holkar State
Context triple: [Rajwada, Indore, associatedWith, Holkar State]
  • A. Kumharsain State
    Kumharsain State was a small princely state in the Himalayan region of British India, historically part of the group of hill states around Simla.
  • B. Holkar State of Indore chosen
    Holkar State of Indore was a prominent Maratha-ruled princely state in central India, centered on the city of Indore and historically governed by the Holkar dynasty.
  • C. Holkar
    Holkar refers to a prominent Maratha dynasty that ruled the Indore State in central India and played a significant role in 18th- and 19th-century Indian politics.
  • D. Basantpur State
    Basantpur State was a small princely hill state located in the Simla Hills region of colonial India.
  • E. Santalpur State
    Santalpur State was a small princely state in western India that historically fell under the jurisdiction of the Palanpur Agency during the British colonial period.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e4f2d0c819091aa3558ea2ee630 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15a2f054c819093fbe173c8a4a544 completed April 29, 2026, 1:09 a.m.
Created at: April 16, 2026, 8:47 p.m.