Triple
T28872850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FHIR Encounter |
E732180
|
entity |
| Predicate | belongsToFHIRVersion |
P80193
|
FINISHED |
| Object | FHIR R4 |
—
|
NE NERFINISHED |
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: FHIR R4 | Statement: [FHIR Encounter, belongsToFHIRVersion, FHIR R4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToFHIRVersion Context triple: [FHIR Encounter, belongsToFHIRVersion, FHIR R4]
-
A.
belongsToVersion
chosen
Indicates that something is associated with, or is a component of, a specific version of an entity or artifact.
-
B.
isVersionOf
Indicates that one entity is a particular version, edition, or variant derived from another entity.
-
C.
isExtendedVersionOf
Indicates that one entity is a longer or more developed form of another, typically adding content or features while preserving the original’s core.
-
D.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
E.
hasVersionFor
Indicates that one entity serves as a specific version or variant tailored for another entity.
- 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_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 28, 2026, 7:34 a.m.