Triple
T22137885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DDDN |
E547078
|
entity |
| Predicate | therapeuticActivities |
P73562
|
FINISHED |
| Object | medical management of digestive diseases |
—
|
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: medical management of digestive diseases | Statement: [DDDN, therapeuticActivities, medical management of digestive diseases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: therapeuticActivities Context triple: [DDDN, therapeuticActivities, medical management of digestive diseases]
-
A.
encouragesActivities
Indicates that one entity promotes, supports, or motivates another entity to engage in certain activities.
-
B.
includesTherapy
chosen
Indicates that one entity contains, offers, or encompasses a specific therapeutic treatment or intervention as part of its scope or composition.
-
C.
activityType
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
-
D.
mannerOfActivity
Indicates the way or style in which an activity is performed or carried out.
-
E.
activitiesCarriedOutFor
Indicates that certain activities are performed on behalf of, in service of, or for the benefit of a particular entity.
- 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129bb78bc8190b74af3a5f6a5348f |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.