Triple
T18116935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MedStar Union Memorial Hospital |
E433627
|
entity |
| Predicate | outpatientCare |
P82392
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [MedStar Union Memorial Hospital, outpatientCare, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outpatientCare Context triple: [MedStar Union Memorial Hospital, outpatientCare, yes]
-
A.
hasAmbulatory
chosen
Indicates that an entity possesses or is provided with ambulatory (walking or outpatient) capabilities or services.
-
B.
medicalPractice
Indicates a relationship where an entity engages in or carries out the professional provision of medical care or services.
-
C.
clinicalSetting
Indicates that an action, observation, or interaction occurs within a healthcare or medical care environment.
-
D.
traditionalCareBy
Indicates that one entity receives traditional or culturally rooted care, treatment, or support from another entity.
-
E.
healthcareType
Indicates the category or kind of healthcare service, system, or coverage associated with an 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd67a2481909d27a4a49b095f8c |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.