Triple
T27077875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D.O. |
E685511
|
entity |
| Predicate | approachToPatientCare |
P149986
|
FINISHED |
| Object | patient-centered |
—
|
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: patient-centered | Statement: [D.O., approachToPatientCare, patient-centered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approachToPatientCare Context triple: [D.O., approachToPatientCare, patient-centered]
-
A.
careApproach
chosen
Indicates the method, strategy, or manner in which care or support is provided to someone or something.
-
B.
focusesOnMedicalCare
Indicates that one entity directs attention, resources, or activity specifically toward providing or improving medical care for another entity.
-
C.
providesComprehensiveCare
Indicates that one entity delivers thorough, wide-ranging support or services addressing multiple needs of another entity.
-
D.
providesCareDuring
Indicates that one entity delivers care, assistance, or support to another entity throughout a specific period or event.
-
E.
positionOnHealthCare
Indicates a person or entity’s stance, opinion, or policy preference regarding health care systems, services, or reforms.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 27, 2026, 8:32 a.m.