Triple

T16608088
Position Surface form Disambiguated ID Type / Status
Subject Phulkian Misl E403495 entity
Predicate hasBranch P35 FINISHED
Object Nabha State
Nabha State was a princely state in colonial India, ruled by a Sikh dynasty and located in the Punjab region.
 E1222713 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: Nabha State | Statement: [Phulkian Misl, hasBranch, Nabha State]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Nabha State
Context triple: [Phulkian Misl, hasBranch, Nabha State]
  • A. Mangal State
    Mangal State was a small princely state in the western Himalayan region of British India, historically grouped among the Simla Hill States.
  • B. Dhar State
    Dhar State was a former princely state in central India, historically ruled by the Pawar (Parmar) Maratha dynasty with its capital at the town of Dhar.
  • C. Wadhwan State
    Wadhwan State was a former princely state in western India, historically significant as a regional center of power and culture under Rajput rule.
  • D. Morvi State
    Morvi State was a former princely state in western India, historically governed by the Jadeja Rajput dynasty.
  • E. Mewar State
    Mewar State was a historic princely state in present-day Rajasthan, India, centered on the city of Udaipur and ruled for centuries by the Sisodia Rajput dynasty.
  • 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: Nabha State
Triple: [Phulkian Misl, hasBranch, Nabha State]
Generated description
Nabha State was a princely state in colonial India, ruled by a Sikh dynasty and located in the Punjab region.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Nabha State
Target entity description: Nabha State was a princely state in colonial India, ruled by a Sikh dynasty and located in the Punjab region.
  • A. Mangal State
    Mangal State was a small princely state in the western Himalayan region of British India, historically grouped among the Simla Hill States.
  • B. Dhar State
    Dhar State was a former princely state in central India, historically ruled by the Pawar (Parmar) Maratha dynasty with its capital at the town of Dhar.
  • C. Wadhwan State
    Wadhwan State was a former princely state in western India, historically significant as a regional center of power and culture under Rajput rule.
  • D. Morvi State
    Morvi State was a former princely state in western India, historically governed by the Jadeja Rajput dynasty.
  • E. Mewar State
    Mewar State was a historic princely state in present-day Rajasthan, India, centered on the city of Udaipur and ruled for centuries by the Sisodia Rajput dynasty.
  • 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_69d883880d0c81908b5fcd454e767b60 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e36093901881909b85af47f75879a9 completed April 18, 2026, 10:44 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0075aa79408190b395d4cd9c6c1cb7 completed May 10, 2026, 12:10 p.m.
NEDg Description generation batch_6a00768e9720819094d4e11ee1e100d6 completed May 10, 2026, 12:14 p.m.
NED2 Entity disambiguation (via description) batch_6a007728680c819082a3bd7e84edb2b0 completed May 10, 2026, 12:16 p.m.
Created at: April 10, 2026, 5:17 a.m.