Triple
T9100186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow maternity hospitals |
E218131
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | healthcare infrastructure element |
C15201
|
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: healthcare infrastructure element Context triple: [Moscow maternity hospitals, instanceOf, healthcare infrastructure element]
-
A.
hospital system facilities
chosen
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.
infrastructure facility
An infrastructure facility is a physical installation or complex that provides essential services or support functions—such as transportation, utilities, communication, or public safety—necessary for the operation and development of a community or region.
-
C.
health care system
A health care system is an organized network of people, institutions, and resources that delivers medical services and public health interventions to maintain and improve the health of a population.
-
D.
healthcare organization unit
A healthcare organization unit is a distinct administrative or functional division within a healthcare system (such as a department, clinic, or ward) that delivers specific health-related services, manages resources, and supports patient care processes.
-
E.
electronic health record system
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.
- 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_69ca83d9844081908e561e367fda6d45 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:15 p.m.