Triple
T25159196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summary Care Record |
E626394
|
entity |
| Predicate | hasPatientRight |
P21381
|
FINISHED |
| Object | right to view their record |
—
|
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: right to view their record | Statement: [Summary Care Record, hasPatientRight, right to view their record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPatientRight Context triple: [Summary Care Record, hasPatientRight, right to view their record]
-
A.
hasPatient
Indicates that an action, event, or process involves a specific entity as the one undergoing or receiving its effects (the patient).
-
B.
hasPatientRole
Indicates that an entity participates in a relationship or activity specifically in the role of a patient (the one receiving care, treatment, or action).
-
C.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
-
D.
hasPatientGroup
Indicates a relationship in which an entity (such as a study, treatment, or clinical activity) is associated with a specific group of patients it involves or targets.
-
E.
hasLegalRight
chosen
Indicates that an entity possesses an officially recognized legal entitlement or permission to perform an action or hold a claim regarding another entity.
- F. None of above.
Provenance (3 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 18, 2026, 6:31 a.m.