Triple
T12079436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MidMichigan Health |
E287638
|
entity |
| Predicate | hasCareSetting |
P3296
|
FINISHED |
| Object | inpatient care |
—
|
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: inpatient care | Statement: [MidMichigan Health, hasCareSetting, inpatient care]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCareSetting Context triple: [MidMichigan Health, hasCareSetting, inpatient care]
-
A.
hasSetting
Indicates that an entity takes place, occurs, or exists within a particular environment, context, or location.
-
B.
hasCareModel
Indicates that one entity uses, follows, or is governed by a particular model or approach to providing care.
-
C.
providesCareSetting
chosen
Indicates that one entity serves as the care environment or setting in which another entity receives or delivers care.
-
D.
hasSettingRole
Indicates that an entity participates in a setting by fulfilling a specific contextual or functional role within it.
-
E.
coversSetting
Indicates that one entity includes or addresses a particular setting or context within its scope.
- 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bf4f508190842927e7e0642235 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:48 p.m.