Triple
T33205142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | erythema nodosum |
E849999
|
entity |
| Predicate | treatmentIncludes |
P122242
|
FINISHED |
| Object | rest |
—
|
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: rest | Statement: [erythema nodosum, treatmentIncludes, rest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatmentIncludes Context triple: [erythema nodosum, treatmentIncludes, rest]
-
A.
includesTreatmentWorks
Indicates that something (such as a plan, project, or system) contains or incorporates specific treatment works or treatment facilities as part of it.
-
B.
treats
Indicates that one entity provides medical care or therapeutic intervention to another entity.
-
C.
treatmentType
chosen
Indicates the specific kind or category of treatment applied or prescribed in relation to an entity or condition.
-
D.
treatmentOf
Indicates a relationship where one entity administers, provides, or is responsible for a therapeutic intervention directed toward another entity (typically a patient or condition).
-
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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:30 a.m.