Gisco (died 239 BC)
ancient Carthaginian general active 241-239 BC

Gisco was a Carthaginian general who served during the closing years of the First Punic War (264–239 BCE) and took a leading part in the events which sparked the Mercenary War. He was a citizen of the city state of Carthage, which was located in what is now Tunisia. His date of birth and age at death are both unknown, as are his activities prior to his rise to prominence towards the end of the First Punic War.
When the Carthaginians conceded defeat in the war in 241 BCE, Gisco was commander of the major base of Lilybaeum (modern Marsala) on Sicily, subordinate to Hamilcar Barca, the overall Carthaginian commander on the island. On being ordered to negotiate a peace treaty, Hamilcar retired to Carthage in a rage, leaving Gisco, as the next most senior commander, in charge of negotiations with the Romans. These resulted in the Treaty of Lutatius, which ended the war. By this time the troops whom he had sent from Sicily to Africa to be repatriated were in a mutinous state over a pay dispute, and Gisco, who had a good reputation with them, was hastily recalled to deal with the situation. The discontent seemed to have abated when, for some unknown reason, discipline broke down. Several soldiers insisted that no deal with Carthage was acceptable, a riot broke out and dissenters were stoned to death. Gisco and his staff were taken prisoner and his treasury was seized.
Begin with the source’s own compact description: “Gisco (died 239 BC)” is ancient Carthaginian general active 241-239 BC. The dossier treats that line as a proposition to test through Gisco, died and ancient, not as a finished interpretation.
Why this record matters
The phrase “ancient Carthaginian general active 241-239 BC” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated May 4, 2026. The linked authority identifier is Q6439549. VIAF identifies the subject as 3086165573983437800000. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Gisco (died 239 BC)”, its source revision and the description used here.
- Expand the search: follow Gisco (died 239 BC) primary sources, Gisco (died 239 BC) archive and Gisco research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Gisco (died 239 BC)”?
- What terminology or title could unlock a more precise catalogue search?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Gisco (died 239 BC)” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.