Triple
T8818786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rohilla chiefs |
E209848
|
entity |
| Predicate | politicalEntityRuled |
P3022
|
FINISHED |
| Object |
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.
|
E765374
|
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: Rohilla state | Statement: [Rohilla chiefs, politicalEntityRuled, Rohilla state]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rohilla state Context triple: [Rohilla chiefs, politicalEntityRuled, Rohilla state]
-
A.
Rajpipla State
Rajpipla State was a former princely state in British India, located in present-day Gujarat.
-
B.
Patdi State
Patdi State was a former princely state in western India historically governed by the Rajput Jhala dynasty.
-
C.
Bijawar State
Bijawar State was a former princely state in British India, located in the Bundelkhand region of present-day Madhya Pradesh.
-
D.
Alwar State
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.
-
E.
Samthar State
Samthar State was a former princely state in colonial India, located in what is now Uttar Pradesh and ruled by a local dynasty under British suzerainty.
- 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: Rohilla state Triple: [Rohilla chiefs, politicalEntityRuled, Rohilla state]
Generated description
Rohilla state was an 18th-century Afghan-ruled polity in northern India, centered in the Rohilkhand region and governed by Rohilla Pashtun chiefs.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Rohilla state Target entity description: Rohilla state was an 18th-century Afghan-ruled polity in northern India, centered in the Rohilkhand region and governed by Rohilla Pashtun chiefs.
-
A.
Rajpipla State
Rajpipla State was a former princely state in British India, located in present-day Gujarat.
-
B.
Patdi State
Patdi State was a former princely state in western India historically governed by the Rajput Jhala dynasty.
-
C.
Bijawar State
Bijawar State was a former princely state in British India, located in the Bundelkhand region of present-day Madhya Pradesh.
-
D.
Alwar State
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.
-
E.
Samthar State
Samthar State was a former princely state in colonial India, located in what is now Uttar Pradesh and ruled by a local dynasty under British suzerainty.
- 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc600e6e2881908934cbff0ab5d6fd |
completed | April 1, 2026, midnight |
| NED1 | Entity disambiguation (via context triple) | batch_69cfab68ff308190b37b2202e7ccbab3 |
completed | April 3, 2026, 11:58 a.m. |
| NEDg | Description generation | batch_69cfaf4a62308190be31c464dbcf0429 |
completed | April 3, 2026, 12:15 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69cfaf9c335881909277236967d1ff54 |
completed | April 3, 2026, 12:16 p.m. |
Created at: March 30, 2026, 6:46 p.m.