A clerk needs party names and case numbers pulled from free-text hearing requests. Which text-analysis approach should they use?

Entity extraction turns free-text civic intake into labeled fields such as party names and case numbers. A clerk processing free-text hearing requests should extract those entities using generative prompting or Foundry Tools text-analysis capabilities so docketing systems receive structured identifiers instead of relying on custom text classification for intent labels, which assigns intent categories without locating the party names and case numbers the docket needs. Generative or tool-assisted extraction is the text-analysis approach matched to unstructured hearing language.

Extracting entities such as party names and case numbers from the free-text requests using custom text classification for intent labels fails because classification assigns broad intent labels, not specific identities, and it is still not the generative-prompting or Foundry Tools extraction approach the stem asks the clerk to use. Extracting entities such as party names and case numbers from the free-text requests using prebuilt key phrase extraction with ranking fails because key phrase extraction surfaces salient topics with importance scores without labeling names or numbers as structured entity fields the docket requires. Extracting entities such as party names and case numbers from the free-text requests using prebuilt PII detection with redaction workflow fails because PII detection masks sensitive personal data for privacy and does not preserve party names or case numbers as structured docket fields.

Exam caveat: extraction can miss nicknames, OCR errors from scanned requests, or ambiguous case-number formats; low-confidence entities need clerk confirmation before filing. Operational check: run entity extraction on sample hearing requests, verify party names and case numbers against the source text, write confirmed entities into the case system, and keep the original free text linked for audit.