Document Anchor
- Last Updated: May 13, 2026
- 1 minute read
- Semaphore
- Documentation
To identify a Document Type we must create a pattern of text, either:
- As anchors that only identify the document and WILL NOT be extracted as facts.
- Those anchors are represented as Document Anchors, which is a direct child concept of the Document Type.
- As facts that both identify the document and WILL be extracted as facts.
- Those facts are represented as Document Facts, which are direct child concepts of the Document Type.
To represent an anchor that will identify a document type and not be extracted, we need to:
- Create a Document Anchor concept.
- Relate the Document Type to the Document Anchor using the correct relationship.
Document Anchor Properties
Mandatory hierarchical relationships
| Label | Range | Constraints |
|---|---|---|
Optional hierarchical relationships
| Label | Range | Constraints |
|---|---|---|
Mandatory associative relationships
| Label | Range | Constraints |
|---|---|---|
Optional associative relationships
| Label | Range | Constraints |
|---|---|---|
Mandatory alternative labels
| Label | Range | Constraints |
|---|---|---|
Optional alternative labels
| Label | Range | Constraints |
|---|---|---|
Mandatory metadata
| Label | Range | Constraints |
|---|---|---|
Optional metadata
| Label | Range | Constraints |
|---|---|---|
| debug | Boolean | only one allowed |