Triple
T28872539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FHIR Binary |
E732175
|
entity |
| Predicate | isTypicallySearchableBy |
P163107
|
FINISHED |
| Object | metadata such as id or securityContext |
—
|
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: metadata such as id or securityContext | Statement: [FHIR Binary, isTypicallySearchableBy, metadata such as id or securityContext]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTypicallySearchableBy Context triple: [FHIR Binary, isTypicallySearchableBy, metadata such as id or securityContext]
-
A.
isSearchable
Indicates that the referenced entity can be discovered or retrieved through a search operation or query.
-
B.
isSoughtIn
Indicates that one entity is being searched for, pursued, or desired within the context, location, or domain of another entity.
-
C.
isIndexedFor
chosen
Indicates that something has been organized or recorded in an index so it can be efficiently located, searched, or retrieved.
-
D.
usedToSearchFor
Indicates that one entity serves as a tool, method, or resource employed to look for, locate, or retrieve another entity.
-
E.
searchingFor
Indicates that one entity is actively seeking, looking for, or attempting to locate 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_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 7:34 a.m.