Triple
T7847158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HIPAA Breach Notification Rule |
E181950
|
entity |
| Predicate | notificationDeadline |
P79339
|
FINISHED |
| Object | without unreasonable delay |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: without unreasonable delay | Statement: [HIPAA Breach Notification Rule, notificationDeadline, without unreasonable delay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notificationDeadline Context triple: [HIPAA Breach Notification Rule, notificationDeadline, without unreasonable delay]
-
A.
hasDeadline
Indicates that an entity is associated with a specific due date or time by which it must be completed or fulfilled.
-
B.
dateOfUltimatum
Indicates the specific date on which an ultimatum was issued, delivered, or came into effect in the relationship between the involved parties.
-
C.
finalDeliveryDate
Indicates the date on which the last or ultimate delivery in a sequence of deliveries is scheduled or actually occurs.
-
D.
delayedBy
Indicates that one event, process, or action occurs later than expected or planned due to the influence or interference of another factor or entity.
-
E.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca8285d6488190a95d4c02d7354b53 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb164105fc8190a60aaa27dd619d5a |
completed | March 31, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69cae92180f88190ae3d44c3de7adc93 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7855a3c81908b9318f7186fc0c0 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:49 p.m.