Triple
T5083805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central India Agency |
E114585
|
entity |
| Predicate | composedOf |
P402
|
FINISHED |
| Object |
Bijawar State
Bijawar State was a former princely state in British India, located in the Bundelkhand region of present-day Madhya Pradesh.
|
E516593
|
NE FINISHED |
How this triple was built (4 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: Bijawar State | Statement: [Central India Agency, composedOf, Bijawar State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bijawar State Context triple: [Central India Agency, composedOf, Bijawar State]
-
A.
Rajpipla State
Rajpipla State was a former princely state in British India, located in present-day Gujarat.
-
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.
Ajaigarh State
Ajaigarh State was a former princely state in British India, located in what is now central India and ruled by a local dynasty under indirect colonial administration.
-
D.
Morvi State
Morvi 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. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Bijawar State Triple: [Central India Agency, composedOf, Bijawar State]
Generated description
Bijawar State was a former princely state in British India, located in the Bundelkhand region of present-day Madhya Pradesh.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Bijawar State Target entity description: Bijawar State was a former princely state in British India, located in the Bundelkhand region of present-day Madhya Pradesh.
-
A.
Rajpipla State
Rajpipla State was a former princely state in British India, located in present-day Gujarat.
-
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.
Ajaigarh State
Ajaigarh State was a former princely state in British India, located in what is now central India and ruled by a local dynasty under indirect colonial administration.
-
D.
Morvi State
Morvi 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. chosen
Provenance (5 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_69bd443e941881908eb4e8c685b6f656 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7517af308190bab5507a9344bf68 |
completed | March 20, 2026, 4:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf330bc5c48190ad8ca1e413b6c68b |
completed | March 22, 2026, 12:08 a.m. |
| NEDg | Description generation | batch_69bf33b60cac8190b62210b23ce90d06 |
completed | March 22, 2026, 12:11 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69bf341dab94819095fe429560cdbbc5 |
completed | March 22, 2026, 12:13 a.m. |
Created at: March 20, 2026, 1:39 p.m.