Triple
T5827687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rewa Kantha Agency |
E129267
|
entity |
| Predicate | includes |
P1393
|
FINISHED |
| Object | Rajpipla State |
E272610
|
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: Rajpipla State | Statement: [Rewa Kantha Agency, includes, Rajpipla State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rajpipla State Context triple: [Rewa Kantha Agency, includes, Rajpipla State]
-
A.
Rajpipla State
chosen
Rajpipla State was a former princely state in British India, located in present-day Gujarat.
-
B.
Bijawar State
Bijawar State was a former princely state in British India, located in the Bundelkhand region of present-day Madhya Pradesh.
-
C.
Samthar State
Samthar State was a former princely state in colonial India, located in what is now Uttar Pradesh and ruled by a local dynasty under British suzerainty.
-
D.
Patdi State
Patdi State was a former princely state in western India historically governed by the Rajput Jhala dynasty.
-
E.
Virpur State
Virpur 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_69c00849d55481908b4f9f5543e0bf6d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0341df8dc8190871af068e1f927a2 |
completed | March 22, 2026, 6:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0bfc62a5c81909fa28f08a49dc919 |
completed | March 23, 2026, 4:21 a.m. |
Created at: March 22, 2026, 3:53 p.m.