Triple
T10149370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dungarpur State |
E232589
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Mewar State |
E741847
|
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: Mewar State | Statement: [Dungarpur State, borderedBy, Mewar State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mewar State Context triple: [Dungarpur State, borderedBy, Mewar State]
-
A.
Mewar State
chosen
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.
-
B.
Panna State
Panna State was a former princely state in central India, historically ruled by Bundela Rajputs and known for its diamond mines and later incorporation into the Indian Union.
-
C.
Morvi State
Morvi State was a former princely state in western India, historically governed by the Jadeja Rajput dynasty.
-
D.
Jaora State
Jaora State was a princely state in British India, located in what is now Madhya Pradesh and ruled by a Muslim dynasty under British suzerainty.
-
E.
Jasdan State
Jasdan 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_69ca84885e48819088a31b127cf44904 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec03e80c81909c813dae91c56272 |
completed | April 2, 2026, 4:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2e6369c848190984394eedf2f07eb |
completed | April 5, 2026, 10:46 p.m. |
Created at: March 30, 2026, 9:08 p.m.