Triple
T20180423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagelkhand Agency |
E492711
|
entity |
| Predicate | hasPrincelyState |
P74995
|
FINISHED |
| Object | Nagod State |
—
|
NE NERFINISHED |
How this triple was built (2 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 Agency, hasPrincelyState, Nagod State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nagod State Context triple: [Bagelkhand Agency, hasPrincelyState, Nagod State]
-
A.
Nagod State
chosen
Nagod State was a former princely state in central India that formed part of the Bagelkhand Agency under British rule.
-
B.
Jasdan State
Jasdan State was a former princely state in western India historically governed by the Jadeja Rajput dynasty.
-
C.
Koti State
Koti State was a small princely state in the Simla Hills region of British India, ruled by local chiefs under British suzerainty.
-
D.
Kalsia State
Kalsia State was a small princely state in colonial India located in the Cis-Sutlej region of present-day Punjab and Haryana.
-
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.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e668edf27881909820f9103e72533e |
completed | April 20, 2026, 5:57 p.m. |
Created at: April 11, 2026, 11:36 p.m.