Triple
T5083800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central India Agency |
E114585
|
entity |
| Predicate | composedOf |
P402
|
FINISHED |
| Object |
Khilchipur State
Khilchipur State was a former princely state in central India that existed under British suzerainty until Indian independence.
|
E508196
|
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: Khilchipur State | Statement: [Central India Agency, composedOf, Khilchipur State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khilchipur State Context triple: [Central India Agency, composedOf, Khilchipur State]
-
A.
Rajpipla State
Rajpipla State was a former princely state in British India, located in present-day Gujarat.
-
B.
Jhalawar State
Jhalawar State was a princely state in British India, located in the southeastern part of present-day Rajasthan and ruled by Jhala Rajput rulers.
-
C.
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.
-
D.
Dholpur State
Dholpur State was a princely state in northern India, ruled by Jat rulers and located in the region that is now part of Rajasthan.
-
E.
Narsinghgarh State
Narsinghgarh State was a former princely state in central India, historically ruled by local royalty 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: Khilchipur State Triple: [Central India Agency, composedOf, Khilchipur State]
Generated description
Khilchipur State was a former princely state in central India that existed under British suzerainty until Indian independence.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Khilchipur State Target entity description: Khilchipur State was a former princely state in central India that existed under British suzerainty until Indian independence.
-
A.
Rajpipla State
Rajpipla State was a former princely state in British India, located in present-day Gujarat.
-
B.
Jhalawar State
Jhalawar State was a princely state in British India, located in the southeastern part of present-day Rajasthan and ruled by Jhala Rajput rulers.
-
C.
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.
-
D.
Dholpur State
Dholpur State was a princely state in northern India, ruled by Jat rulers and located in the region that is now part of Rajasthan.
-
E.
Narsinghgarh State
chosen
Narsinghgarh State was a former princely state in central India, historically ruled by local royalty under British suzerainty.
- F. None of above.
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_69bd443e941881908eb4e8c685b6f656 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7517af308190bab5507a9344bf68 |
completed | March 20, 2026, 4:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf186790248190bc94cfbecf3cfe73 |
completed | March 21, 2026, 10:15 p.m. |
| NEDg | Description generation | batch_69bf18f90d9081908a47e69e82ed2940 |
completed | March 21, 2026, 10:17 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69bf195e7be88190a7655d18471b1662 |
completed | March 21, 2026, 10:19 p.m. |
Created at: March 20, 2026, 1:39 p.m.