Triple
T19254821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagelkhand |
E481487
|
entity |
| Predicate | historicalPrincelyState |
P74995
|
FINISHED |
| Object |
Nagod State
Nagod State was a former princely state in central India that formed part of the Bagelkhand Agency under British rule.
|
E1366661
|
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: Nagod State | Statement: [Bagelkhand, historicalPrincelyState, Nagod State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nagod State Context triple: [Bagelkhand, historicalPrincelyState, Nagod State]
-
A.
Jasdan State
Jasdan State was a former princely state in western India historically governed by the Jadeja Rajput dynasty.
-
B.
Koti State
Koti State was a small princely state in the Simla Hills region of British India, ruled by local chiefs under British suzerainty.
-
C.
Kalsia State
Kalsia State was a small princely state in colonial India located in the Cis-Sutlej region of present-day Punjab and Haryana.
-
D.
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.
-
E.
Ulwar State
Ulwar State was a former princely state in British India, located in the region of present-day Rajasthan.
- 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: Nagod State Triple: [Bagelkhand, historicalPrincelyState, Nagod State]
Generated description
Nagod State was a former princely state in central India that formed part of the Bagelkhand Agency under British rule.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Nagod State Target entity description: Nagod State was a former princely state in central India that formed part of the Bagelkhand Agency under British rule.
-
A.
Jasdan State
Jasdan State was a former princely state in western India historically governed by the Jadeja Rajput dynasty.
-
B.
Koti State
Koti State was a small princely state in the Simla Hills region of British India, ruled by local chiefs under British suzerainty.
-
C.
Kalsia State
Kalsia State was a small princely state in colonial India located in the Cis-Sutlej region of present-day Punjab and Haryana.
-
D.
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.
-
E.
Ulwar State
Ulwar State was a former princely state in British India, located in the region of present-day Rajasthan.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb3459d08190a7c28ed3f8c82a97 |
completed | April 20, 2026, 10:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0705e746688190888834aa0206ac07 |
completed | May 15, 2026, 11:39 a.m. |
| NEDg | Description generation | batch_6a0706d7c63c8190a7114937af40b294 |
completed | May 15, 2026, 11:43 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a070763ca5c81908afa73b30645223a |
completed | May 15, 2026, 11:45 a.m. |
Created at: April 10, 2026, 1:28 p.m.