Triple
T30087541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lateral sulcus |
E764637
|
entity |
| Predicate | visibleOnImaging |
P67713
|
FINISHED |
| Object | MRI of brain |
—
|
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: MRI of brain | Statement: [lateral sulcus, visibleOnImaging, MRI of brain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibleOnImaging Context triple: [lateral sulcus, visibleOnImaging, MRI of brain]
-
A.
hasImagingFinding
chosen
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).
-
B.
visibleUnder
Indicates that one entity can be seen or perceived when another specified condition, context, or covering entity is present or in effect.
-
C.
isDifficultToObserveInVisible
Indicates that the subject cannot be easily detected or studied using visible-wavelength (optical) observations.
-
D.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
E.
visibilityInImages
Indicates how clearly or prominently an entity can be seen or detected within one or more images.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d6de8a081909e426dcdf9fe0536 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:04 p.m.