Triple
T2460600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajpipla |
E54523
|
entity |
| Predicate | stateCapitalOf |
P6344
|
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: [Rajpipla, stateCapitalOf, Rajpipla State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rajpipla State Context triple: [Rajpipla, stateCapitalOf, Rajpipla State]
-
A.
Rajpipla State
chosen
Rajpipla State was a former princely state in British India, located in present-day Gujarat.
-
B.
Virpur State
Virpur State was a former princely state in western India historically governed by the Jadeja Rajput dynasty.
-
C.
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.
-
D.
Morvi State
Morvi State was a former princely state in western India, historically governed by the Jadeja Rajput dynasty.
-
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_69ab49dee84c819096b50a0049c347ac |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd10ba66481909580e994b22fd406 |
completed | March 7, 2026, 7:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af2b77207481909037a6ab4b420168 |
completed | March 9, 2026, 8:20 p.m. |
Created at: March 6, 2026, 9:44 p.m.