Triple
T36829382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Şahsiyet |
E910095
|
entity |
| Predicate | hasDiseaseDepicted |
P182538
|
FINISHED |
| Object | Alzheimer’s disease |
—
|
NE NERFINISHED |
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: Alzheimer’s disease | Statement: [Şahsiyet, hasDiseaseDepicted, Alzheimer’s disease]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiseaseDepicted Context triple: [Şahsiyet, hasDiseaseDepicted, Alzheimer’s disease]
-
A.
diseaseDepicted
chosen
Indicates that a visual representation (such as an image or illustration) shows or portrays a particular disease.
-
B.
depictsMedicalCondition
Indicates that one entity visually represents or illustrates a particular medical condition affecting another entity or subject.
-
C.
hasAssociatedDisease
Indicates that an entity is linked to, or commonly occurs with, a particular disease or medical condition.
-
D.
hasTargetDisease
Indicates that an entity (such as a treatment, study, or intervention) is directed toward, intended to affect, or primarily concerned with a specified disease.
-
E.
hasEponymousDisease
Indicates that an entity (typically a person) has a disease named after them.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: May 3, 2026, 4:13 p.m.