Triple
T33205356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simponi |
E850003
|
entity |
| Predicate | combinationTherapyWith |
P70673
|
FINISHED |
| Object | methotrexate |
—
|
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: methotrexate | Statement: [Simponi, combinationTherapyWith, methotrexate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combinationTherapyWith Context triple: [Simponi, combinationTherapyWith, methotrexate]
-
A.
actsSynergisticallyWith
Indicates that two entities interact in a way that enhances or amplifies each other's effects or outcomes beyond what they would achieve independently.
-
B.
combinationType
Indicates how multiple elements are combined or related to each other within a composite structure or operation.
-
C.
combinedIn
chosen
Indicates that two or more entities are merged, joined, or used together to form a single combined whole or context.
-
D.
introducedFromCombinationOf
Indicates that something is newly created or arises as a result of combining two or more other entities or elements.
-
E.
therapyWith
Indicates that one entity receives or engages in therapeutic treatment or counseling with another entity (such as a therapist, therapy method, or therapeutic resource).
- 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_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:30 a.m.