Triple

T33245741
Position Surface form Disambiguated ID Type / Status
Subject infliximab-axxq E851093 entity
Predicate hasBiosimilarRelationship P37220 FINISHED
Object highly similar to reference infliximab 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: highly similar to reference infliximab | Statement: [infliximab-axxq, hasBiosimilarRelationship, highly similar to reference infliximab]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBiosimilarRelationship
Context triple: [infliximab-axxq, hasBiosimilarRelationship, highly similar to reference 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. hasBispecificity
    Indicates that an entity (typically a molecule or antibody) possesses specificity for two distinct targets or binding sites simultaneously.
  • D. relatedDrug
    Indicates that one drug has a specified relationship or association with another drug, such as interaction, similarity, or therapeutic linkage.
  • 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_69f34962386c81909ddc3bf9e18ddeb8 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f74062b9388190b30546cf700a825c completed May 3, 2026, 12:32 p.m.
PD Predicate disambiguation batch_69f73c802b848190b61a416b7488bd96 completed May 3, 2026, 12:16 p.m.
Created at: May 1, 2026, 1:31 a.m.