Triple

T18116934
Position Surface form Disambiguated ID Type / Status
Subject MedStar Union Memorial Hospital E433627 entity
Predicate inpatientCare P30112 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, inpatientCare, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inpatientCare
Context triple: [MedStar Union Memorial Hospital, inpatientCare, yes]
  • A. hospitalizedIn
    Indicates that a person or patient is admitted for medical care and staying as an inpatient in a specified hospital or healthcare facility.
  • B. containsHospital
    Indicates that one entity includes or encompasses a hospital within its boundaries or composition.
  • C. requiresQualifyingHospitalStayFor
    Indicates that one entity must have a prior qualifying hospital stay as a prerequisite condition for another entity (such as a service, benefit, or coverage) to apply.
  • D. isAcuteCareFacility
    Indicates that the entity functions as a healthcare facility providing short-term, intensive medical treatment for patients with severe or urgent conditions.
  • E. hasInpatientBeds chosen
    Indicates that an entity provides or is equipped with beds designated for admitting and treating inpatients.
  • 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.