Triple
T5601154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jhala dynasty |
E147122
|
entity |
| Predicate | ruled |
P760
|
FINISHED |
| Object |
Patdi State
Patdi State was a former princely state in western India historically governed by the Rajput Jhala dynasty.
|
E551494
|
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: Patdi State | Statement: [Jhala dynasty, ruled, Patdi State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Patdi State Context triple: [Jhala dynasty, ruled, Patdi State]
-
A.
Narsinghgarh State
Narsinghgarh State was a former princely state in central India, historically ruled by local royalty under British suzerainty.
-
B.
Rajpipla State
Rajpipla State was a former princely state in British India, located in present-day Gujarat.
-
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: Patdi State Triple: [Jhala dynasty, ruled, Patdi State]
Generated description
Patdi State was a former princely state in western India historically governed by the Rajput Jhala dynasty.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Patdi State Target entity description: Patdi State was a former princely state in western India historically governed by the Rajput Jhala dynasty.
-
A.
Narsinghgarh State
Narsinghgarh State was a former princely state in central India, historically ruled by local royalty under British suzerainty.
-
B.
Rajpipla State
Rajpipla State was a former princely state in British India, located in present-day Gujarat.
-
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_69c009043d648190a7af89698ccf1e3e |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020da519c81908626b243e40db263 |
completed | March 22, 2026, 5:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0a142ae8c8190a8c4a02bb3f69ff2 |
completed | March 23, 2026, 2:11 a.m. |
| NEDg | Description generation | batch_69c0a1faf7d48190ad2d5f43ef37da82 |
completed | March 23, 2026, 2:14 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c0a2e17cd88190a54f5166fe5c654a |
completed | March 23, 2026, 2:18 a.m. |
Created at: March 22, 2026, 3:39 p.m.