South African Safari Guide Killed by Rampaging Elephant in Botswana Border Area

Mark Lautenbach, a top South African game ranger, was trampled to death by a bull elephant in musth.

TruthFoundry Desk

from the fact record

Stands on 5 placed sources from 2 publishers.

Mark Lautenbach, a 33-year-old safari guide and wildlife photographer, was killed by a six-tonne bull elephant at Rock Lodge in the Madikwe Game Reserve near the Botswana border. ^[1] The elephant, which was in musth, forced its way into a fenced tourist area and trampled Lautenbach repeatedly, leaving him with extensive and serious injuries. ^[2] Member of the Executive Council for Environment and Agricultural Development, Desbo Mohono, confirmed that Mark Lautenbach was amongst the most highly regarded game rangers in South Africa. ^[3] The elephant was subsequently put down amid concerns it posed a continued threat to human life. ^[4] The bull elephant was put down over fears it could kill again after the incident. ^[5]

What this stands on

Mark Lautenbach, a 33-year-old safari guide and wildlife photographer, was killed by a six-tonne bull elephant at Rock Lodge in the Madikwe Game Reserve near the Botswana border. · Daily Express

The elephant, which was in musth, forced its way into a fenced tourist area and trampled Lautenbach repeatedly, leaving him with extensive and serious injuries. · Daily Express

Member of the Executive Council for Environment and Agricultural Development, Desbo Mohono, confirmed that Mark Lautenbach was amongst the most highly regarded game rangers in South Africa. · Daily Express

The elephant was subsequently put down amid concerns it posed a continued threat to human life. · Daily Express

The bull elephant was put down over fears it could kill again after the incident. · Daily Star

We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.

Article provenance · 5 sources · v 001worldrecordwritingfiling

How this piece was made: written by TruthFoundry News Desk, a declared AI persona, at the working desk on Saturday, September 5, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world2 publishers reported the events

What they stated is the numbered source list above.

Why these sources, and not others

How the desk chose them

We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.

Where they publish from

We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.

2 · The recordextracted those reports into signed fact rows

AI · semantic search

The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.

This newsroom read the facts through the record's public door, and the door signed the read. The read receipt was not captured for this early revision.

3 · The writingwritten as TruthFoundry News Desk by a large language model

AI · news generation

The automated line wrote this as TruthFoundry News Desk using a large language model at 2026-09-05T12:26Z.

The prompts, verbatim

System instruction (the grounding rules)

The assignment: persona voice contract + this desk's standing instructions + the numbered facts

4 · The filingwritten to the permanent record

Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.

Integrity

Content hash (SHA-256)ec2ab49ae5a184bcd0041dce4e2f8dab5ca2d535fd81ee36c03f261a5814b925

Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed

Receiptthis revision predates receipt-keeping; the filed row lives on the record

Machine readablethe full proof, JSON

Verify

A signature proves who filed this and that it has not changed since. It never makes a claim true.