Triple
T3777645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CT scanner |
E83345
|
entity |
| Predicate | modalityOf |
P50872
|
FINISHED |
| Object | radiology |
—
|
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: radiology | Statement: [CT scanner, modalityOf, radiology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modalityOf Context triple: [CT scanner, modalityOf, radiology]
-
A.
usesModality
Indicates that an action, communication, or process is carried out through or characterized by a particular modality (such as visual, auditory, tactile, or another mode of expression or operation).
-
B.
modeType
Indicates the specific manner, method, or operational mode in which an action, process, or system is carried out or functions.
-
C.
mode
Indicates the manner, method, or way in which an action, process, or interaction is carried out or occurs.
-
D.
modulates
Indicates that one entity adjusts, regulates, or alters the intensity, frequency, or effect of another entity or process.
-
E.
usesModulation
Indicates that one entity applies or employs a particular modulation method or scheme in relation to another entity or process.
- 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc5d3dbc8190b6ab118a56acd5a3 |
completed | March 8, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69adc050cc5c81909d9855f866f3c26d |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc0fe3e3c8190bd886c7745c172a0 |
completed | March 8, 2026, 6:33 p.m. |
Created at: March 8, 2026, 3:36 p.m.