Triple
T26492737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doppler ultrasound |
E669200
|
entity |
| Predicate | usesContrastAgents |
P168574
|
FINISHED |
| Object | sometimes |
—
|
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: sometimes | Statement: [Doppler ultrasound, usesContrastAgents, sometimes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesContrastAgents Context triple: [Doppler ultrasound, usesContrastAgents, sometimes]
-
A.
hasVolumeContrasts
Indicates that an entity exhibits notable differences in loudness or intensity across its parts or over time.
-
B.
usesRadiation
Indicates that an entity employs radiation as a means or component in performing an action, process, or function.
-
C.
hasCTScans
Indicates that one entity possesses, is associated with, or includes one or more CT scan imaging records related to another entity.
-
D.
providesContrastWith
Indicates that one entity is used to highlight differences or distinctions when compared with another entity.
-
E.
achievesContrast
Indicates that one entity creates or enhances a visual or conceptual difference relative to another entity.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 27, 2026, 1:05 a.m.