Triple
T13817139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | thallium |
E332046
|
entity |
| Predicate | radioisotopeUse |
P36680
|
FINISHED |
| Object | myocardial perfusion 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: myocardial perfusion imaging | Statement: [thallium, radioisotopeUse, myocardial perfusion imaging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioisotopeUse Context triple: [thallium, radioisotopeUse, myocardial perfusion imaging]
-
A.
usedRadioisotope
chosen
Indicates that one entity employed or applied a specific radioisotope in an action, process, or context involving another entity.
-
B.
appliedRadioisotopesIn
Indicates that radioisotopes were used or applied within a specified context, process, or location.
-
C.
radioisotopesReleased
Indicates that radioactive isotopes are emitted or discharged from a source into the surrounding environment.
-
D.
radioactiveIsotopesDetected
Indicates that the presence of radioactive isotopes has been detected in or associated with the referenced entity or context.
-
E.
radioactivity
Indicates that an entity emits ionizing radiation due to unstable atomic nuclei undergoing radioactive decay.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0281bb988190803ee195f430b9c8 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc862e9608190bd8a3d883959b7e4 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:12 p.m.