Triple
T28872540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FHIR Binary |
E732175
|
entity |
| Predicate | oftenReferencedFrom |
P179033
|
FINISHED |
| Object | DocumentReference |
—
|
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: DocumentReference | Statement: [FHIR Binary, oftenReferencedFrom, DocumentReference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenReferencedFrom Context triple: [FHIR Binary, oftenReferencedFrom, DocumentReference]
-
A.
alsoRefersTo
Indicates that one term, label, or identifier is used as an alternative designation for the same entity or concept as another.
-
B.
oftenRefersTo
Indicates that one entity is frequently used to mention, denote, or reference another entity in common usage or context.
-
C.
isFrequentlyReferencedAs
Indicates that one entity is commonly or repeatedly mentioned, cited, or referred to by another entity or within a particular context.
-
D.
isReferencedIn
Indicates that one entity is cited, mentioned, or otherwise referred to within another entity.
-
E.
referredTo
Indicates that one entity has mentioned, directed attention to, or cited another entity as a point of reference.
- 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_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71995853c8190912025c0e83640c8 |
completed | May 3, 2026, 9:47 a.m. |
Created at: April 28, 2026, 7:34 a.m.