Ambiguous relation

Business ruleSpace Specifications

A link (note: Link) between two entities (note: Entity) fell (3 passages, no note) back to the generic relation (note: Relation) because no section (note: Section), no typed attribute (4 passages, no note) and no single allowed relation decided it. It is kept at a capped confidence (note: Confidence). The finding (note: Finding) is raised (4 passages, no note) by the relation typing (note: Relation typing) step (note: Step) and points at the note the link (3 passages, no note) was read in, on the line of its first located provenance (note: Provenance); a link that co-occurrences (note: Co-occurrence) alone know raises nothing, since a co-occurrence names no file and is unnamed by nature.

Check (note: Check) I-REL-AMBIGUOUS, severity (note: Severity) info (8 passages, no note) by default, documented with a before and after example in the check pages. The severity can be overridden per project (note: Project) or per repository (note: Knowledge repository).

Applies to

Properties4

Domain
Quality
Status
valid
Severity
info

4 declared keys. The rest of the file is free text.

On this page1

  1. Applies to
See the neighbourhood map6 pages6Neighbourhood mapAmbiguous relation

Neighbourhood map Ambiguous relation

Distance1 hop

Neighbourhood map. The list below carries the same information as the map.existing pageword without a note

51 neighbours in total, more than the map shows.

textual equivalent

Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.