Triple
T300384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HL7 standards |
E6183
|
entity |
| Predicate | includes |
P1393
|
FINISHED |
| Object | HL7 FHIR |
E6183
|
NE 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: HL7 FHIR | Statement: [HL7 standards, includes, HL7 FHIR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HL7 FHIR Context triple: [HL7 standards, includes, HL7 FHIR]
-
A.
HL7 standards
chosen
HL7 standards are a widely adopted set of international specifications for the exchange, integration, sharing, and retrieval of electronic health information between healthcare systems.
-
B.
Health Connect
Health Connect is a unified health and fitness data platform on Android that lets apps securely share and manage users’ wellness information in one place.
-
C.
SNOMED CT
SNOMED CT is a comprehensive, multilingual clinical healthcare terminology used worldwide to standardize the recording and sharing of medical information in electronic health records.
-
D.
Cerner
Cerner is a major American health information technology company best known for its electronic health record (EHR) systems and healthcare data solutions.
-
E.
IHE Patient Care Device profiles
IHE Patient Care Device profiles are interoperability specifications that define how medical devices integrate and exchange data within healthcare IT systems to support safe, coordinated patient care.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2e9e6a8308190b9bd15310e324504 |
completed | Feb. 28, 2026, 1:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3aba14b0881908eb4f62ac9261d63 |
completed | March 1, 2026, 2:59 a.m. |
Created at: Feb. 28, 2026, 1:06 p.m.