Triple

T14250308
Position Surface form Disambiguated ID Type / Status
Subject Hennepin County Medical Center E353242 entity
Predicate hasEmergencyDesignation P55749 FINISHED
Object regional trauma center 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: regional trauma center | Statement: [Hennepin County Medical Center, hasEmergencyDesignation, regional trauma center]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEmergencyDesignation
Context triple: [Hennepin County Medical Center, hasEmergencyDesignation, regional trauma center]
  • A. hasEmergencyLevel chosen
    Indicates that an entity is associated with a specific degree or severity of emergency status.
  • B. hasCriticalDesignation
    Indicates that an entity has been assigned a status or label marking it as critical in importance, priority, or required attention.
  • C. hasEmergencyUse
    Indicates that an entity is authorized, designated, or configured for use specifically in emergency situations or conditions.
  • D. hasEmergencyServiceProvider
    Indicates that an entity is associated with or served by a specific emergency service provider (such as police, fire, or medical services).
  • E. hasEmergencyAlarm
    Indicates that an entity is equipped with or associated with an emergency alarm system that can be activated in urgent situations.
  • 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_69d8278c43e08190824146f4632b89a5 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de6296f9d0819086f62f525d07eb12 completed April 14, 2026, 3:51 p.m.
PD Predicate disambiguation batch_69de05c09b7881908acbca18bd7d997c completed April 14, 2026, 9:15 a.m.
Created at: April 10, 2026, 1:08 a.m.