Triple
T33254614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SUS |
E851340
|
entity |
| Predicate | regionHealthcareSystem |
P15635
|
FINISHED |
| Object | Region Skåne healthcare system |
—
|
NE NERFINISHED |
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: Region Skåne healthcare system | Statement: [SUS, regionHealthcareSystem, Region Skåne healthcare system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionHealthcareSystem Context triple: [SUS, regionHealthcareSystem, Region Skåne healthcare system]
-
A.
healthSystem
chosen
Indicates a relationship where an entity functions as, belongs to, or is managed within a particular health care system or network.
-
B.
healthSystemLevel
Indicates the level or tier within a health system at which a given action, service, or relationship occurs (e.g., local, regional, national).
-
C.
locatedInHealthRegion
Indicates that an entity is situated within the geographic or administrative boundaries of a specified health region.
-
D.
shareHealthSystem
Indicates that two entities are served by, or belong to, the same healthcare system or network.
-
E.
isRegionalHospital
Indicates that a hospital serves as a primary medical center for a specific geographic region, providing comprehensive healthcare services to that area.
- 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_69f34963135c819084e7f1d483421f00 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff1e3e13c08190bb8990c44716b746 |
completed | May 9, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_69ff1dfcaf2c8190aaf2b428d57b7782 |
completed | May 9, 2026, 11:43 a.m. |
Created at: May 1, 2026, 1:31 a.m.