Triple
T28872538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FHIR Binary |
E732175
|
entity |
| Predicate | isTypicallyNotSearchableBy |
P152676
|
FINISHED |
| Object | content |
—
|
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: content | Statement: [FHIR Binary, isTypicallyNotSearchableBy, content]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTypicallyNotSearchableBy Context triple: [FHIR Binary, isTypicallyNotSearchableBy, content]
-
A.
isSearchable
Indicates that the referenced entity can be discovered or retrieved through a search operation or query.
-
B.
notTypicallyShownTo
Indicates that one entity is generally not displayed or presented to another entity under normal circumstances.
-
C.
isSoughtIn
Indicates that one entity is being searched for, pursued, or desired within the context, location, or domain of another entity.
-
D.
notAccessibleBy
Indicates that one entity cannot be reached, used, or obtained through another specified entity or means.
-
E.
notDirectlyAvailableFor
chosen
Indicates that an entity cannot be accessed, used, or obtained immediately or without intermediaries, but may be reachable through indirect means or additional steps.
- 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_69f65a4842588190835ef304e918d03a |
completed | May 2, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:34 a.m.