Triple
T28872852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FHIR Encounter |
E732180
|
entity |
| Predicate | hasResourceTypeCode |
P3729
|
FINISHED |
| Object | Encounter |
—
|
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: Encounter | Statement: [FHIR Encounter, hasResourceTypeCode, Encounter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResourceTypeCode Context triple: [FHIR Encounter, hasResourceTypeCode, Encounter]
-
A.
hasTypeCode
Indicates that an entity is associated with a specific type classification represented by a code.
-
B.
hasTypeOfResource
chosen
Indicates that an entity is associated with a specific category or kind of resource it represents or utilizes.
-
C.
hasRecordType
Indicates that an entity is associated with or classified under a specific type or category of record.
-
D.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
hasHistoricResourceType
Indicates that an entity is associated with a particular category or type of historic resource.
- F. None of above.
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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69ff891e4b9c8190aa86a339a8944496 |
completed | May 9, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69ff8801180c8190b23e20996ca68e0a |
completed | May 9, 2026, 7:16 p.m. |
Created at: April 28, 2026, 7:34 a.m.