Triple
T28872417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FHIR DocumentReference |
E732174
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | FHIR resource |
C49393
|
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: FHIR resource Context triple: [FHIR DocumentReference, instanceOf, FHIR resource]
-
A.
FHIR version
A FHIR version represents a specific, uniquely identified release of the FHIR standard that defines the structure, behavior, and semantics of FHIR resources and interactions.
-
B.
FHIR release
A FHIR release is a specific published version of the FHIR standard that bundles defined resources, specifications, and implementation guidance for use in healthcare interoperability.
-
C.
health information exchange interoperability profile
A health information exchange interoperability profile is a standardized specification that defines how different healthcare systems and applications should structure, secure, and exchange electronic health data to ensure consistent, reliable, and seamless information sharing.
-
D.
NHS core system
The NHS core system is a centralized digital infrastructure that securely manages, integrates, and provides access to patient records, clinical workflows, and administrative services across the National Health Service.
-
E.
RDF resource
chosen
An RDF resource is any identifiable entity (real or abstract) that can be uniquely referenced by a URI and described using RDF statements.
- 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:34 a.m.