Triple
T21699171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeast Health |
E535606
|
entity |
| Predicate | offersSpecialtyCare |
P144958
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Southeast Health, offersSpecialtyCare, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersSpecialtyCare Context triple: [Southeast Health, offersSpecialtyCare, true]
-
A.
hasSpecialty
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
B.
openingSpecialty
Indicates the specific area of focus, expertise, or type associated with an opening (such as a job, position, or opportunity).
-
C.
hasSpecialist
Indicates that one entity is associated with or assigned to a specialist entity that provides expert support, service, or oversight for it.
-
D.
supportsMedicalSpecialty
Indicates that one entity provides resources, infrastructure, or services that enable or facilitate the practice or development of a particular medical specialty.
-
E.
hasHealthcareServicesIn
Indicates that a healthcare provider or organization offers or operates healthcare services within a specified location or area.
- 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_69e0c46a6ee481908836e1420fb78c9b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef9b7de9888190bbca7717a32f9888 |
completed | April 27, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:45 p.m.