Triple
T22400354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baghela Rajput dynasty |
E553740
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object |
Bandhogarh
Bandhogarh is a historic fortress and former royal seat in central India, renowned as the erstwhile stronghold of the Baghela Rajput rulers.
|
E1537258
|
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: Bandhogarh | Statement: [Baghela Rajput dynasty, capital, Bandhogarh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bandhogarh Context triple: [Baghela Rajput dynasty, capital, Bandhogarh]
-
A.
Rajgarh
Rajgarh is a town in the Indian state of Rajasthan, known as one of the settlements within the Alwar district.
-
B.
Rajgarh
Rajgarh is a town in the Sirmour district of Himachal Pradesh, India, known for its hilly terrain, orchards, and role as a local administrative and market center.
-
C.
Rajgarh
Rajgarh is a town and administrative district headquarters in the central Indian state of Madhya Pradesh, known for its agricultural economy and historical temples.
-
D.
Sujangarh
Sujangarh is a town in the Indian state of Rajasthan known for its local markets, temples, and role as a regional commercial center.
-
E.
Deogarh
Deogarh was a historic kingdom ruled by the Gonds, an indigenous community in central India.
- 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: Bandhogarh Triple: [Baghela Rajput dynasty, capital, Bandhogarh]
Generated description
Bandhogarh is a historic fortress and former royal seat in central India, renowned as the erstwhile stronghold of the Baghela Rajput rulers.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Bandhogarh Target entity description: Bandhogarh is a historic fortress and former royal seat in central India, renowned as the erstwhile stronghold of the Baghela Rajput rulers.
-
A.
Rajgarh
Rajgarh is a town in the Indian state of Rajasthan, known as one of the settlements within the Alwar district.
-
B.
Rajgarh
Rajgarh is a town in the Sirmour district of Himachal Pradesh, India, known for its hilly terrain, orchards, and role as a local administrative and market center.
-
C.
Rajgarh
Rajgarh is a town and administrative district headquarters in the central Indian state of Madhya Pradesh, known for its agricultural economy and historical temples.
-
D.
Sujangarh
Sujangarh is a town in the Indian state of Rajasthan known for its local markets, temples, and role as a regional commercial center.
-
E.
Deogarh
Deogarh was a historic kingdom ruled by the Gonds, an indigenous community in central India.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158b39c908190a735aa860d733869 |
completed | April 29, 2026, 1:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0b0c6263048190a1c5a28cc00ec780 |
completed | May 18, 2026, 12:56 p.m. |
| NEDg | Description generation | batch_6a0b0d10a50881909fb586a3c529623d |
completed | May 18, 2026, 12:58 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0b0daf9bac819086166985458f6742 |
completed | May 18, 2026, 1:01 p.m. |
Created at: April 16, 2026, 8:46 p.m.