Triple
T33219618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | infliximab-qbtx |
E850384
|
entity |
| Predicate | isBiosimilarOf |
P37220
|
FINISHED |
| Object | infliximab |
—
|
NE NERFINISHED |
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: infliximab | Statement: [infliximab-qbtx, isBiosimilarOf, infliximab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBiosimilarOf Context triple: [infliximab-qbtx, isBiosimilarOf, infliximab]
-
A.
hasBiosimilar
chosen
Indicates that one biological product is a biosimilar counterpart to another reference biological product.
-
B.
notableBiosimilarArea
Indicates that an entity is significantly involved in, or recognized for, work related to a particular biosimilar product or therapeutic area.
-
C.
isProdrugOf
Indicates that one substance is a precursor form that is metabolized in the body to produce the active form of another substance.
-
D.
bioequivalence
Indicates that two pharmaceutical products have no significant difference in their bioavailability and effect at the site of action when administered at the same molar dose under similar conditions.
-
E.
hasCommonDoseStrength
Indicates that two medicinal products share at least one identical dosage strength.
- 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_69f3496083dc8190b229bb6932dc548b |
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.