Triple
T19626839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Bhopal |
E471157
|
entity |
| Predicate | effectOnMarathas |
P136759
|
FINISHED |
| Object | expanded Maratha political influence |
—
|
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: expanded Maratha political influence | Statement: [Battle of Bhopal, effectOnMarathas, expanded Maratha political influence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnMarathas Context triple: [Battle of Bhopal, effectOnMarathas, expanded Maratha political influence]
-
A.
strength_Maratha_side
Indicates the level or extent of military or combat power associated with the Maratha side in a conflict or comparison.
-
B.
effectOnMysore
Indicates the impact or influence that something has on Mysore.
-
C.
sideInBattleOfBuxar
Indicates being a participating side or party in the Battle of Buxar.
-
D.
effectOnCossacks
Indicates the impact or consequences that something has on Cossacks as a group.
-
E.
tacticsUsedByMughals
Indicates the military tactics or strategies that were employed by the Mughals.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640eadcc48190ab5e36ddcde0c328 |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:44 p.m.