CACrown ArchivesThe cinema collection
Menu
Research dossier · General Reference

Elafin

mammalian protein found in Homo sapiens

Cross-disciplinary reference desk with index cards, atlas, dictionary and catalogue
General referenceInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionJul 15, 2025
Entity authorityQ5353128
Source-derived summary

Elafin, also known as peptidase inhibitor 3 or skin-derived antileukoprotease (SKALP), is a protein that in humans is encoded by the PI3 gene.

Function

This gene encodes an elastase-specific protease inhibitor, which contains a WAP-type four-disulfide core (WFDC) domain, and is thus a member of the WFDC domain family. Most WFDC gene members are localized to chromosome 20q12-q13 in two clusters: centromeric and telomeric. This gene belongs to the centromeric cluster.

Clinical significance

Elafin has been found to have utility in serving as a biomarker for graft versus host disease of the skin.

Elafin plays some role in gut inflammation.

Editorial summary

The public source identifies “Elafin” as mammalian protein found in Homo sapiens. This brief keeps that definition visible, then builds a research path around Elafin, mammalian and protein.

Editorial reviewA concise reference frame for defining the subject, testing terminology and identifying the institution closest to the evidence. The current 100-word lead offers orientation but no explicit four-digit date, so chronology should not be assumed. The selected authority fields contribute no independent date. Its value is orientation rather than verdict, with Elafin, mammalian and protein providing the first useful test.
Editorial analysis

Why this record matters

A short description can identify a subject without explaining its stakes. For “Elafin”, the useful work is to connect “mammalian protein found in Homo sapiens” to the records capable of establishing context and consequence.

Evidence profile

Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Jul 15, 2025. The linked authority identifier is Q5353128. None of the 0 selected statements returned an explicit reference.

Critical limits

Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. 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.

Best used for
  • Subject orientation
  • Search vocabulary
  • Locating named sources
Verify next

The closest primary source, responsible institution and strongest cited specialist reference.

Three-step research path

  1. Establish the record: confirm the title “Elafin”, its source revision and the description used here.
  2. Expand the search: follow Elafin primary sources, Elafin archive and Elafin research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “Elafin”?
  2. Which institution is responsible for the underlying evidence?
  3. What terminology or title could unlock a more precise catalogue search?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from Elafin” 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.