Triple
T28872891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FHIR Encounter |
E732180
|
entity |
| Predicate | usesClassSystem |
P180787
|
FINISHED |
| Object | http://terminology.hl7.org/CodeSystem/v3-ActCode |
—
|
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: http://terminology.hl7.org/CodeSystem/v3-ActCode | Statement: [FHIR Encounter, usesClassSystem, http://terminology.hl7.org/CodeSystem/v3-ActCode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesClassSystem Context triple: [FHIR Encounter, usesClassSystem, http://terminology.hl7.org/CodeSystem/v3-ActCode]
-
A.
usesClass
Indicates that one entity makes use of, depends on, or is implemented using a particular class in its structure or behavior.
-
B.
hasObjectSystem
Indicates that something is associated with, contains, or is part of a particular object system.
-
C.
usedByClass
Indicates that something (such as a resource, method, or component) is utilized or depended upon by a particular class.
-
D.
includesClasses
Indicates that one entity contains or encompasses one or more class-type entities as part of its definition or structure.
-
E.
isClassOf
Indicates that one entity is a class or category to which another entity belongs or is an instance of.
- F. None of above. chosen
Provenance (4 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
| PDg | Predicate description generation | batch_69f7516c538481908c6e55cf76add098 |
completed | May 3, 2026, 1:45 p.m. |
Created at: April 28, 2026, 7:34 a.m.