Triple
T28871635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Query/Retrieve Service Class |
E732158
|
entity |
| Predicate | supportsInformationModel |
—
|
GENERATED |
| Object | Patient Root Information Model |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInformationModel Context triple: [Query/Retrieve Service Class, supportsInformationModel, Patient Root Information Model]
-
A.
supportedModel
Indicates that one entity provides compatibility with, or operational backing for, a particular model.
-
B.
supportsModelingOf
Indicates that one entity provides the capability or functionality needed to represent, simulate, or model another entity or process.
-
C.
supportsModelType
chosen
Indicates that an entity is compatible with, or can operate using, a specified model type.
-
D.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
E.
dataSupports
Indicates that one piece of data provides evidence, justification, or backing for the validity or reliability of another piece of data, claim, or conclusion.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 7:33 a.m.