Triple
T13131149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman medicine |
E311967
|
entity |
| Predicate | hasTherapy |
P73562
|
FINISHED |
| Object | dietetic therapy |
—
|
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: dietetic therapy | Statement: [Roman medicine, hasTherapy, dietetic therapy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTherapy Context triple: [Roman medicine, hasTherapy, dietetic therapy]
-
A.
includesTherapy
chosen
Indicates that one entity contains, offers, or encompasses a specific therapeutic treatment or intervention as part of its scope or composition.
-
B.
hasTherapyContext
Indicates that an entity is associated with, occurs within, or is characterized by a specific therapeutic setting, framework, or treatment context.
-
C.
hasTherapeuticGoal
Indicates that an action, treatment, or intervention is undertaken with the intention of achieving a specific therapeutic or health-related outcome.
-
D.
hasReceivedTreatmentFor
Indicates that an entity has undergone or been given a treatment in relation to a specified condition, issue, or problem.
-
E.
usesTreatment
Indicates that one entity applies or employs a particular treatment or therapeutic method on or for another 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981b27a8c81909a92ab7be5d3a7e9 |
completed | April 10, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:07 p.m.