Abstract
NoAbstract schemata are used for inheritance only and shouldn’t be used directly.
Call
Since v1.26.0Inheritance
graph BT
Call(Call)
Interval(Interval)
click Interval "/explorer/schemata/Interval"
class Call node-primary
Call-->Interval
Info
Generated
YesEntities using a generated schema shouldn’t be created directly by users.
Matchable
NoEntities using a matchable schema can be used for matching and cross-referencing.
Hidden
NoEntities using a hidden schema shouldn’t be displayed in user interfaces or created by users.
Semantics
FollowTheMoney has well-defined semantics for different representations of entities, for example in a network graph or in a timeline.
- In a network graph, entities should be represented as a vertex.
-
In a timeline,
dateorstartDateshould be used as the temporal start.endDateshould be used as the temporal end. - Call entities have no temporal extent, i.e. they are not suitable for representation in a timeline.
Properties
| Name | Label | Type |
|---|---|---|
Call:caller
|
Caller | LegalEntity |
Call:callerNumber
|
Caller's Number | phone |
Call:receiver
|
Receiver | LegalEntity |
Call:receiverNumber
|
Receiver's Number | phone |
Interval:alephUrl
|
Aleph URL | url |
Interval:date
|
Date | date |
Interval:description
|
Description | text |
Call:duration
|
Duration | number |
Interval:endDate
|
End date | date |
Interval:indexText
|
Index text | text |
Interval:modifiedAt
|
Modified on | date |
Interval:namesMentioned
|
Detected names | name |
Interval:publisher
|
Publishing source | string |
Interval:publisherUrl
|
Publishing source URL | url |
Interval:recordId
|
Record ID | string |
Interval:retrievedAt
|
Retrieved on | date |
Interval:sourceUrl
|
Source link | url |
Interval:startDate
|
Start date | date |
Interval:summary
|
Summary | text |