Triple
T9683997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jhalawar State |
E234357
|
entity |
| Predicate | hasBorderWith |
P224
|
FINISHED |
| Object | Tonk State |
E211322
|
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: Tonk State | Statement: [Jhalawar State, hasBorderWith, Tonk State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tonk State Context triple: [Jhalawar State, hasBorderWith, Tonk State]
-
A.
Tonk State
chosen
Tonk State was a princely state in British India, notable for being one of the few Muslim-ruled states in the largely Rajput-dominated region of present-day Rajasthan.
-
B.
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.
-
C.
Patdi State
Patdi State was a former princely state in western India historically governed by the Rajput Jhala dynasty.
-
D.
Dhar State
Dhar State was a former princely state in central India, historically ruled by the Pawar (Parmar) Maratha dynasty with its capital at the town of Dhar.
-
E.
Morvi State
Morvi State was a former princely state in western India, historically governed by the Jadeja Rajput dynasty.
- 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_69ca84c99e34819092e5563a7106cfca |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9ccf21a08190a1302b933b9e50be |
completed | April 1, 2026, 10:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19106e67881909505287620d2f781 |
completed | April 4, 2026, 10:30 p.m. |
Created at: March 30, 2026, 8:16 p.m.