Triple

T16665846
Position Surface form Disambiguated ID Type / Status
Subject Imperial Service Troops E404978 entity
Predicate raisedFrom P18556 FINISHED
Object Alwar State E205377 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: Alwar State | Statement: [Imperial Service Troops, raisedFrom, Alwar State]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Alwar State
Context triple: [Imperial Service Troops, raisedFrom, Alwar State]
  • A. Alwar State chosen
    Alwar State was a princely state in northern India, ruled by Rajput princes and later integrated into the modern state of Rajasthan after Indian independence.
  • B. Alirajpur State
    Alirajpur State was a former princely state in colonial India, located in what is now Madhya Pradesh and ruled by local Rajput chiefs under British suzerainty.
  • C. Patdi State
    Patdi State was a former princely state in western India historically governed by the Rajput Jhala dynasty.
  • D. Ali Rajpur State
    Ali Rajpur State was a former princely state in British India, historically administered under the Rewa Kantha Agency in what is now western India.
  • E. Rohilla state
    Rohilla state was an 18th-century Afghan-ruled polity in northern India, centered in the Rohilkhand region and governed by Rohilla Pashtun chiefs.
  • 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_69d8838b5fbc81908c6575c132b82e80 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e37c9cd7ec819084aa9b2830874bf5 completed April 18, 2026, 12:44 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00c79657ec8190b1b3500b7a99df0a completed May 10, 2026, 5:59 p.m.
Created at: April 10, 2026, 5:18 a.m.