Triple
T5566161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miami Valley Hospital |
E145883
|
entity |
| Predicate | neonatalICULevel |
P64825
|
FINISHED |
| Object | Level III |
—
|
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: Level III | Statement: [Miami Valley Hospital, neonatalICULevel, Level III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neonatalICULevel Context triple: [Miami Valley Hospital, neonatalICULevel, Level III]
-
A.
hasIntensiveCareUnit
Indicates that a medical facility includes and operates an intensive care unit (ICU) for critically ill patients.
-
B.
isOnlyLevelITraumaCenterFor
Indicates that one entity serves as the sole Level I trauma center available to another specified region or population.
-
C.
hasICD10Code
Indicates that an entity is associated with a specific ICD-10 diagnostic code used for classifying diseases and health conditions.
-
D.
numberOfHospitalized
Indicates the count of individuals who have been admitted to a hospital for medical care.
-
E.
ApgarScoreComponents
Indicates the specific component measurements that together constitute an overall Apgar score assessment.
- F. None of above. chosen
Provenance (4 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_69c008fdae24819081aa002ad99cd966 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02034fc3081908920c52a19d462e1 |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b12826c8190969a584d0f53aa44 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f4032408190a4f0d2eb21ebd870 |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:36 p.m.