Triple
T19172732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garha-Mandla |
E469364
|
entity |
| Predicate | RaniDurgavatiRole |
P134712
|
FINISHED |
| Object | queen and regent of Garha-Mandla |
—
|
LITERAL 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: queen and regent of Garha-Mandla | Statement: [Garha-Mandla, RaniDurgavatiRole, queen and regent of Garha-Mandla]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RaniDurgavatiRole Context triple: [Garha-Mandla, RaniDurgavatiRole, queen and regent of Garha-Mandla]
-
A.
roleInShivajisLife
Indicates the specific role, influence, or significance an entity had in the life of Shivaji.
-
B.
predecessorAsMaharajaOfGwalior
Indicates that one entity previously held the position of Maharaja of Gwalior immediately before another entity.
-
C.
roleInAkbarsLife
Indicates the specific role, position, or significance that one entity held in relation to Akbar’s life.
-
D.
roleAtPanipat
Indicates the specific role, position, or function an entity held in relation to the Battle of Panipat.
-
E.
roleInCarnaticWars
Indicates the role or involvement an entity had in the events of the Carnatic Wars.
- F. None of above. chosen
Provenance (4 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f16544948190bd10ca7804dd27a5 |
completed | April 20, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:06 p.m.