Triple
T31820074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern California trauma referral region |
E812234
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | trauma referral region |
C262
|
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: trauma referral region Context triple: [Northern California trauma referral region, instanceOf, trauma referral region]
-
A.
regional hospital system
A regional hospital system is an organized network of hospitals and related healthcare facilities within a specific geographic area that coordinates services, resources, and administration to provide comprehensive medical care to the local population.
-
B.
tertiary care center
A tertiary care center is a specialized healthcare facility that provides advanced, highly specialized diagnostic, therapeutic, and surgical services typically unavailable at primary or secondary care institutions.
-
C.
region
chosen
A region is a bounded area within a larger space, defined by shared characteristics, properties, or relationships that distinguish it from surrounding areas.
-
D.
emergency medical services facility
An emergency medical services facility is a specialized healthcare site equipped and staffed to provide immediate assessment, stabilization, and life-saving treatment to patients with urgent or critical medical conditions.
-
E.
emergency services provider
An emergency services provider is an organization or individual that delivers urgent, often life-saving assistance in response to crises, accidents, or disasters, such as medical emergencies, fires, or public safety threats.
- 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:45 p.m.