Triple
T29606118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basic Patient Privacy Consents |
E754580
|
entity |
| Predicate | representsConsentAs |
P193543
|
FINISHED |
| Object | CDA document |
—
|
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: CDA document | Statement: [Basic Patient Privacy Consents, representsConsentAs, CDA document]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsConsentAs Context triple: [Basic Patient Privacy Consents, representsConsentAs, CDA document]
-
A.
consentType
Indicates the specific kind or category of consent that has been given, requested, or recorded in the relationship.
-
B.
consentAuthority
Indicates that one entity has the legal or formal authority to give, withhold, or manage consent on behalf of another entity or for a particular action or process.
-
C.
hasGivenConsentFor
Indicates that one entity has granted permission or approval for a specific action, process, or use involving another entity or resource.
-
D.
isConsentOrder
Indicates that a given legal or regulatory decision is a consent order, i.e., an order entered by agreement of the involved parties rather than imposed unilaterally.
-
E.
consentIssue
Indicates that there is a problem, concern, or irregularity related to obtaining, giving, or validating consent between the involved entities.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69fd49f612a4819096fe7d5a3bb439ba |
completed | May 8, 2026, 2:27 a.m. |
Created at: April 28, 2026, 6:25 p.m.