Triple
T972849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alzheimer's disease |
E20980
|
entity |
| Predicate | managementIncludes |
P22712
|
FINISHED |
| Object | cognitive stimulation |
—
|
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: cognitive stimulation | Statement: [Alzheimer's disease, managementIncludes, cognitive stimulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managementIncludes Context triple: [Alzheimer's disease, managementIncludes, cognitive stimulation]
-
A.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
B.
staffIncluded
Indicates that staff members are included or provided as part of the associated entity, service, or arrangement.
-
C.
workIncludes
Indicates that a work (such as a project, document, or creative piece) contains or incorporates another specified component, part, or element.
-
D.
manager
Indicates that one entity holds a supervisory or administrative role with authority and responsibility over another entity.
-
E.
includesOrganization
Indicates that one entity contains, encompasses, or has within it the specified organization as a component, member, or part.
- 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b44c38f08190997e141d424e9e04 |
completed | March 1, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a6aa2c8190aebba71320ab678f |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b38630848190bd3898a4f42018ad |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:40 p.m.