Triple
T37853211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Salher |
E944111
|
entity |
| Predicate | combatantStrengthMarathas |
P39452
|
FINISHED |
| Object | approximately 40,000 cavalry |
—
|
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: approximately 40,000 cavalry | Statement: [Battle of Salher, combatantStrengthMarathas, approximately 40,000 cavalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantStrengthMarathas Context triple: [Battle of Salher, combatantStrengthMarathas, approximately 40,000 cavalry]
-
A.
strength_Maratha_side
chosen
Indicates the level or extent of military or combat power associated with the Maratha side in a conflict or comparison.
-
B.
sideInBattleOfHaldighati
Indicates participation as a particular side or faction in the Battle of Haldighati.
-
C.
sideInBattleOfPanipat
Indicates participation as a particular side or faction in the Battle of Panipat.
-
D.
effectOnMarathas
Indicates the impact or consequences that something has on the Marathas.
-
E.
opponentInBattleOfHaldighati
Indicates that two entities stood on opposing sides as adversaries in the Battle of Haldighati.
- 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:19 p.m.