Triple
T5511571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jadeja dynasty |
E144576
|
entity |
| Predicate | notableState |
P18999
|
FINISHED |
| Object | Morvi State |
E105124
|
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: Morvi State | Statement: [Jadeja dynasty, notableState, Morvi State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Morvi State Context triple: [Jadeja dynasty, notableState, Morvi State]
-
A.
Morvi State
chosen
Morvi State was a former princely state in western India, historically governed by the Jadeja Rajput dynasty.
-
B.
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.
-
C.
Bijawar State
Bijawar State was a former princely state in British India, located in the Bundelkhand region of present-day Madhya Pradesh.
-
D.
Virpur State
Virpur State was a former princely state in western India historically governed by the Jadeja Rajput dynasty.
-
E.
Jhabua State
Jhabua State was a former princely state in western India, located in what is now Madhya Pradesh and historically ruled by Rajput chiefs under British suzerainty.
- 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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f4cbc2c819091fcbff5f39ceeb4 |
completed | March 22, 2026, 4:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c04cbaca1c8190a7f6d4001f43749c |
completed | March 22, 2026, 8:10 p.m. |
Created at: March 22, 2026, 3:33 p.m.