Triple

T33292125
Position Surface form Disambiguated ID Type / Status
Subject Ko143 E852343 entity
Predicate selectivityProfile P150059 FINISHED
Object more selective for BCRP than for P-glycoprotein 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: more selective for BCRP than for P-glycoprotein | Statement: [Ko143, selectivityProfile, more selective for BCRP than for P-glycoprotein]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: selectivityProfile
Context triple: [Ko143, selectivityProfile, more selective for BCRP than for P-glycoprotein]
  • A. ligandFamily
    Indicates that one entity is a ligand belonging to the same functional or structural family as another entity.
  • B. substrateAffinity
    Indicates the degree to which one entity tends to bind to, interact with, or preferentially act upon a particular substrate.
  • C. hasDrugBankID
    Indicates that an entity is associated with a specific identifier from the DrugBank database.
  • D. substrateSpecificity chosen
    Indicates that an enzyme or catalyst selectively acts on, binds to, or transforms particular substrate molecules over others.
  • E. receptorTypeInteractedWith
    Indicates that one entity has interacted with, bound to, or otherwise engaged a specific type of receptor.
  • 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_69f349660ff48190a4568803d0b89941 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6f8164698819090c1b471f1caa4c6 completed May 3, 2026, 7:24 a.m.
PD Predicate disambiguation batch_69f6f6619404819084662aef1238261c completed May 3, 2026, 7:16 a.m.
Created at: May 1, 2026, 1:32 a.m.