Triple
T2543331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Assaye |
E57837
|
entity |
| Predicate | strength_Maratha_side |
P39452
|
FINISHED |
| Object | over 30,000 troops |
—
|
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: over 30,000 troops | Statement: [Battle of Assaye, strength_Maratha_side, over 30,000 troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strength_Maratha_side Context triple: [Battle of Assaye, strength_Maratha_side, over 30,000 troops]
-
A.
commandingForce2Strength
Indicates that a commanding force possesses or exerts a particular level or measure of strength.
-
B.
commandingForce1Strength
Indicates that one entity has a certain level or measure of strength in its role as the primary commanding force over another entity or situation.
-
C.
strengthBritishCavalry
Indicates the numerical or qualitative level of military power or effectiveness possessed by British cavalry forces.
-
D.
combatantStrength
Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
-
E.
besiegingForce
Indicates a military group that is surrounding and attacking a target location or force in an attempt to capture or subdue it.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2bf6cac819083a9ab9d041d8641 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1c7b6e48190be9a0c31069df797 |
completed | March 7, 2026, 7:20 a.m. |
Created at: March 6, 2026, 9:47 p.m.