Triple
T25231916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aliya Rama Raya |
E632237
|
entity |
| Predicate | resultOfBattleOfTalikota |
P19109
|
FINISHED |
| Object | capture and execution by Deccan forces |
—
|
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: capture and execution by Deccan forces | Statement: [Aliya Rama Raya, resultOfBattleOfTalikota, capture and execution by Deccan forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfBattleOfTalikota Context triple: [Aliya Rama Raya, resultOfBattleOfTalikota, capture and execution by Deccan forces]
-
A.
effectOnMarathas
Indicates the impact or consequences that something has on the Marathas.
-
B.
sideInBattleOfBuxar
Indicates being a participating side or party in the Battle of Buxar.
-
C.
basedOnInVikramarjunaVijaya
Indicates that something is derived, adapted, or takes its source material from the work *Vikramarjuna Vijaya*.
-
D.
resultOfMilitaryCampaign
Indicates that one event, condition, or outcome occurs as a direct consequence of a specified military campaign.
-
E.
resultOfBattle
chosen
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
- F. None of above.
Provenance (3 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 21, 2026, 1:06 p.m.