Triple
T20147436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S II |
E491339
|
entity |
| Predicate | usedInImagingTechnique |
P38700
|
FINISHED |
| Object | narrowband imaging |
—
|
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: narrowband imaging | Statement: [S II, usedInImagingTechnique, narrowband imaging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInImagingTechnique Context triple: [S II, usedInImagingTechnique, narrowband imaging]
-
A.
imagedIn
Indicates that one entity appears within or is depicted in an image associated with another entity.
-
B.
usesRadiation
Indicates that an entity employs radiation as a means or component in performing an action, process, or function.
-
C.
hasImagingFinding
Indicates that an entity (typically a patient, case, or anatomical region) is associated with a specific observation or result identified through an imaging procedure (e.g., X-ray, CT, MRI).
-
D.
usedByTechnique
chosen
Indicates that a particular technique makes use of or employs the referenced entity as part of its method or process.
-
E.
usedRadioisotope
Indicates that one entity employed or applied a specific radioisotope in an action, process, or context involving 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6679f43bc8190a1cd4768b3e87505 |
completed | April 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69e54cfd924881909b55f3e4d3e7e070 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:33 p.m.