Orites excelsus
species of plant

Orites excelsus, commonly known as prickly ash, mountain silky oak or white beefwood, is a species of flowering plant in the family Proteaceae and is endemic to eastern Australia. It is a medium-sized to tall rainforest tree with oblong to lance-shaped leaves, variously lobed and with teeth on the edges. The flowers are white and arranged in leaf axils in spikes that are shorter than the leaves.
Description
Orites excelsus is a tree that typically grows to a height of up to 30 m (98 ft) with more or less smooth brown or grey bark, often with minute scales, and new shoots are covered with rust-coloured hairs at first. The leaves are elliptic, lance-shaped, egg-shaped or oblong, 40–185 mm (1.6–7.3 in) long and 15–45 mm (0.59–1.77 in) wide on a petiole 10–25 mm (0.39–0.98 in) long. They are usually lobed, usually have teeth regularly arranged along the edges, shiny green on the upper surface and grey to whitish below. The flowers are white or creamy-white, fragrant, about 6 mm (0.24 in) long and are arranged in leaf axils along a rachis 50–110 mm (2.0–4.3 in) long. Flowering occurs from winter to early spring and the follicles are boat-shaped, 20–30 mm (0.79–1.18 in) long and 8–10 mm (0.31–0.39 in) wide.
Taxonomy
Orites excelsus was first formally described in 1830 by Robert Brown in Supplementum primum Prodromi florae Novae Hollandiae from specimens collected by Charles Fraser near the Hastings River in 1818.
Frederick Manson Bailey described Orites fragrans from Mounts Bellenden Ker and Bartle Frere, now accepted as an isonym of O. excelsus.
The public source identifies “Orites excelsus” as species of plant. This brief keeps that definition visible, then builds a research path around Orites, excelsus and species.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Orites excelsus”, the useful work is to connect “species of plant” to the records capable of establishing context and consequence.
The date and method of observation matter as much as the stated conclusion, especially where classification or consensus has changed. The source revision retrieved here is dated Mar 4, 2026. The linked authority identifier is Q3012756. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1830 and 1818.
Scientific names, classifications and consensus can change while older terminology persists in catalogues and historical literature. 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
Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.
- Current terminology
- Classification context
- Finding cited technical literature
Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.
Three-step research path
- Establish the record: confirm the title “Orites excelsus”, its source revision and the description used here.
- Expand the search: follow Orites excelsus primary sources, Orites excelsus archive and Orites 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 “Orites excelsus”?
- Has classification or technical consensus changed since the cited source?
- Which observation, specimen, dataset or publication supports the account?
Search terms from this dossier
This entry incorporates text from “Orites excelsus” 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.