Triple
T30087587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lenticulostriate arteries |
E764638
|
entity |
| Predicate | imagingAppearance |
P133181
|
FINISHED |
| Object | small deep infarcts on MRI |
—
|
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: small deep infarcts on MRI | Statement: [lenticulostriate arteries, imagingAppearance, small deep infarcts on MRI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imagingAppearance Context triple: [lenticulostriate arteries, imagingAppearance, small deep infarcts on MRI]
-
A.
photographicAppearance
Indicates that one entity visually appears in a photograph or photographic representation of another entity.
-
B.
segmentAppearance
Indicates how a particular segment is visually or perceptually presented or manifested.
-
C.
imagedIn
Indicates that one entity appears within or is depicted in an image associated with another entity.
-
D.
describesAppearanceOf
Indicates that one entity provides information about the visual characteristics or outward look of another entity.
-
E.
hasTypicalAppearance
chosen
Indicates that an entity exhibits the standard or commonly expected visual form or look associated with its kind.
- 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_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:04 p.m.