Triple
T32836452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Techirghiol |
E839844
|
entity |
| Predicate | therapeuticIndications |
P113308
|
FINISHED |
| Object | rheumatic 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: rheumatic diseases | Statement: [Techirghiol, therapeuticIndications, rheumatic diseases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: therapeuticIndications Context triple: [Techirghiol, therapeuticIndications, rheumatic diseases]
-
A.
treatmentIndication
chosen
Indicates that a treatment is intended to address, alleviate, or prevent a particular condition, symptom, or medical indication.
-
B.
potentialTherapeuticUse
Indicates that something is being considered or investigated as a possible treatment or therapy for a condition or disease.
-
C.
therapeuticSubgroup
Indicates a relationship where one entity is classified as a therapeutic subgroup within the broader therapeutic categorization of another entity.
-
D.
coreTherapeuticArea
Indicates the primary medical or clinical domain in which a therapy, treatment, or product is principally intended to be used.
-
E.
diseaseUsed
Indicates that a particular disease is employed or utilized as a tool, model, or condition within a given context or process.
- 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_69f3493ff0888190b51e974eae2a7834 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:16 a.m.