Triple

T15446829
Position Surface form Disambiguated ID Type / Status
Subject Treaty of Mandeswar (1818) E370044 entity
Predicate signatory P173 FINISHED
Object Holkar State E296940 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: Holkar State | Statement: [Treaty of Mandeswar (1818), signatory, Holkar State]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Holkar State
Context triple: [Treaty of Mandeswar (1818), signatory, 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. Jahangir Nagar
    Jahangir Nagar is the former Mughal-era name of present-day Dhaka, given in honor of the emperor Jahangir.
  • 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_69d85a19180081909925012fbf4e62a3 completed April 10, 2026, 2:02 a.m.
NER Named-entity recognition batch_69e03ef767b4819099f2c0919a158321 completed April 16, 2026, 1:44 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff21adb6b88190b573068bda223892 completed May 9, 2026, 11:59 a.m.
Created at: April 10, 2026, 3:21 a.m.