Triple
T33316300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OCKTask |
E853025
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | CareKit model type |
C61129
|
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: CareKit model type Context triple: [OCKTask, instanceOf, CareKit model type]
-
A.
CareKit component
chosen
A CareKit component is a modular, reusable UI or data element within Apple’s CareKit framework that represents and manages a specific aspect of a patient’s care experience, such as tasks, symptoms, or insights.
-
B.
HealthKit class
A HealthKit class represents a structured interface for accessing, storing, and managing a user’s health-related data—such as activity, biometrics, and medical records—within a unified, privacy-aware framework.
-
C.
HealthKit API
HealthKit API is a framework that enables apps to securely access, store, and share users’ health and fitness data on Apple devices in a centralized, privacy-focused manner.
-
D.
FHIR resource type
A FHIR resource type is a standardized, modular data structure defined by the FHIR specification to represent specific kinds of healthcare information (such as patients, observations, or medications) for interoperable exchange between systems.
-
E.
HomeKit framework class
A HomeKit framework class represents an abstraction of a HomeKit entity (such as an accessory, service, or characteristic) that enables apps to discover, configure, and control smart home devices within Apple’s Home ecosystem.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:33 a.m.