Triple
T10827661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GNU Health |
E255535
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hospital information system |
C16823
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: hospital information system Context triple: [GNU Health, instanceOf, hospital information system]
-
A.
hospital system facilities
A hospital system facilities class represents the physical infrastructure, equipment, and support services that enable the delivery of healthcare across one or more hospital locations.
-
B.
hospital
A hospital is a healthcare facility where medical professionals diagnose, treat, and care for patients using specialized equipment and services.
-
C.
electronic health record system
chosen
An electronic health record system is a digital platform that securely collects, stores, manages, and shares patients’ health information to support clinical care, coordination, and decision-making.
-
D.
public hospital network
A public hospital network is a coordinated system of government-funded hospitals and healthcare facilities that collaboratively provide accessible, often low-cost or free, medical services to a defined population or region.
-
E.
health informatics organization
A health informatics organization is an entity that develops, manages, and applies information systems and data standards to improve the collection, exchange, analysis, and use of health information for clinical, administrative, and public health purposes.
- F. None of above.
Provenance (1 batch)
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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:19 p.m.