Triple
T20180422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagelkhand Agency |
E492711
|
entity |
| Predicate | hasPrincelyState |
P74995
|
FINISHED |
| Object | Maihar State |
—
|
NE NERFINISHED |
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: Maihar State | Statement: [Bagelkhand Agency, hasPrincelyState, Maihar State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maihar State Context triple: [Bagelkhand Agency, hasPrincelyState, Maihar State]
-
A.
Maihar State
chosen
Maihar State was a former princely state in central India, historically part of the Bagelkhand Agency, known for its royal patronage of Hindustani classical music and the Maihar gharana.
-
B.
Morvi State
Morvi State was a former princely state in western India, historically governed by the Jadeja Rajput dynasty.
-
C.
Mangal State
Mangal State was a small princely state in the western Himalayan region of British India, historically grouped among the Simla Hill States.
-
D.
Virpur State
Virpur State was a former princely state in western India historically governed by the Jadeja Rajput dynasty.
-
E.
Ulwar State
Ulwar State was a former princely state in British India, located in the region of present-day Rajasthan.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e668edf27881909820f9103e72533e |
completed | April 20, 2026, 5:57 p.m. |
Created at: April 11, 2026, 11:36 p.m.