Triple

T9030911
Position Surface form Disambiguated ID Type / Status
Subject Sirohi State E216168 entity
Predicate alternativeName P39 FINISHED
Object Sirohi Princely State E216168 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: Sirohi Princely State | Statement: [Sirohi State, alternativeName, Sirohi Princely State]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sirohi Princely State
Context triple: [Sirohi State, alternativeName, Sirohi Princely State]
  • A. Jhalawar State
    Jhalawar State was a princely state in British India, located in the southeastern part of present-day Rajasthan and ruled by Jhala Rajput rulers.
  • B. Kishangarh State
    Kishangarh State was a princely state in colonial India, ruled by Rajput princes and located in the region historically known as Rajputana (now largely in Rajasthan).
  • C. Pratapgarh State
    Pratapgarh State was a princely state in western India, historically ruled by Rajput chiefs and later integrated into the Indian Union after independence.
  • D. Sirohi State chosen
    Sirohi State was a princely state in western India, ruled by Rajput chiefs and later integrated into the Indian Union after independence.
  • E. Dholpur State
    Dholpur State was a princely state in northern India, ruled by Jat rulers and located in the region that is now part of Rajasthan.
  • 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_69ca83a5fa88819088144801b4dd7245 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc6a9e0aa881908886f453c51ecd0e completed April 1, 2026, 12:45 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfdbc662208190a3f4e6e593208c5c completed April 3, 2026, 3:24 p.m.
Created at: March 30, 2026, 7:08 p.m.