The property isRecordedAt is defined as a subproperty of gist:actualEndDateTime. So, if I have a bank transaction event ex:_Transaction_123 that was completed three days before it was recorded, I want two things in the triple store:

1. when was the transaction itself completed
2. when was the record of the transaction created.

For the first, I can say
ex:_Transaction_123 gist:actualEndMinute '2021-06-01T08:32:00'^^xsd:dateTime # June 1, 2021

But if I also say:
ex:_Transaction_123 gist:isRecordedAt '2021-06-04T08:32:00'^^xsd:dateTime # June 4, 2021 then I can infer from the subproperty axioms that
ex:_Transaction_123 gist:actualEndDateTime '2021-06-01T08:32:00'^^xsd:dateTime # June 4, 2021

So now the same transaction has two different end times. The problem is that isRecordedAt is the end time of the recording event, not the event being recorded. So isRecordedAt cannot be a subproperty of gist:actualEndDateTime.

This just came up in client work