Triple

T21217639
Position Surface form Disambiguated ID Type / Status
Subject Palanpur Agency E522877 entity
Predicate hasTerritorialUnit P8351 FINISHED
Object 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.
 E1481528 NE FINISHED

How this triple was built (4 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: Santalpur State | Statement: [Palanpur Agency, hasTerritorialUnit, Santalpur State]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Santalpur State
Context triple: [Palanpur Agency, hasTerritorialUnit, Santalpur State]
  • A. Basantpur State
    Basantpur State was a small princely hill state located in the Simla Hills region of colonial India.
  • B. Narsinghgarh State
    Narsinghgarh State was a former princely state in central India, historically ruled by local royalty under British suzerainty.
  • C. Santrampur State
    Santrampur State was a former princely state in British India, located in what is now the state of Gujarat.
  • D. 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.
  • E. Mundhar State
    Mundhar State was a small princely hill state located in the Simla Hills region of colonial India.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Santalpur State
Triple: [Palanpur Agency, hasTerritorialUnit, Santalpur State]
Generated description
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.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Santalpur State
Target entity description: 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.
  • A. Basantpur State
    Basantpur State was a small princely hill state located in the Simla Hills region of colonial India.
  • B. Narsinghgarh State
    Narsinghgarh State was a former princely state in central India, historically ruled by local royalty under British suzerainty.
  • C. Santrampur State
    Santrampur State was a former princely state in British India, located in what is now the state of Gujarat.
  • D. 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.
  • E. Mundhar State
    Mundhar State was a small princely hill state located in the Simla Hills region of colonial India.
  • F. None of above. chosen

Provenance (5 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_69e0b511ed84819099b449b4a111085c completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7347613308190a1c9f4ea51591d4b completed April 21, 2026, 8:25 a.m.
NED1 Entity disambiguation (via context triple) batch_6a09b40e435c8190b8277bbc99c5552b completed May 17, 2026, 12:26 p.m.
NEDg Description generation batch_6a09b4cc6f8081908b0ad1ce87b47e70 completed May 17, 2026, 12:30 p.m.
NED2 Entity disambiguation (via description) batch_6a09b79237908190bf90b4316b58c7b1 completed May 17, 2026, 12:41 p.m.
Created at: April 16, 2026, 3:41 p.m.