Triple

T6233220
Position Surface form Disambiguated ID Type / Status
Subject Advocate Lutheran General Hospital E139406 entity
Predicate hasNeonatalICULevel 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: [Advocate Lutheran General Hospital, hasNeonatalICULevel, Level III]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNeonatalICULevel
Context triple: [Advocate Lutheran General Hospital, hasNeonatalICULevel, Level III]
  • A. neonatalICULevel chosen
    Indicates the level or tier of care provided by a neonatal intensive care unit (NICU) in relation to the newborn patient.
  • B. hasIntensiveCareUnit
    Indicates that a medical facility includes and operates an intensive care unit (ICU) for critically ill patients.
  • C. hasICD10Code
    Indicates that an entity is associated with a specific ICD-10 diagnostic code used for classifying diseases and health conditions.
  • D. isOnlyLevelITraumaCenterFor
    Indicates that one entity serves as the sole Level I trauma center available to another specified region or population.
  • E. hospitalizedIn
    Indicates that a person or patient is admitted for medical care and staying as an inpatient in a specified hospital or healthcare facility.
  • 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_69c008b0e7ac8190808a59573ee646f3 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c062efa25c8190a54f5a6f5b5ad24f completed March 22, 2026, 9:45 p.m.
PD Predicate disambiguation batch_69c05601de6481909d0880048fd7b49a completed March 22, 2026, 8:50 p.m.
Created at: March 22, 2026, 4:22 p.m.