Triple
T8877433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dholpur State |
E211321
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Bharatpur State |
E208181
|
NE FINISHED |
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: Bharatpur State | Statement: [Dholpur State, borderedBy, Bharatpur State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bharatpur State Context triple: [Dholpur State, borderedBy, Bharatpur State]
-
A.
Bharatpur State
chosen
Bharatpur State was a princely state in pre-independence India, ruled by Jat rulers and located in the region that is now part of Rajasthan.
-
B.
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.
-
C.
Udaipur State
Udaipur State was a princely state in present-day Rajasthan, India, historically ruled by the Sisodia Rajput dynasty from its capital at Udaipur.
-
D.
Rajgarh State
Rajgarh State was a former princely state in central India that existed under British suzerainty until Indian independence.
-
E.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69ca838e78748190934d82db3104f855 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61496870819097c55c73aca62aac |
completed | April 1, 2026, 12:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfc92c2f088190b953de2bfcbb5bb5 |
completed | April 3, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:52 p.m.