Triple

T22796831
Position Surface form Disambiguated ID Type / Status
Subject LOXO-195 E564270 entity
Predicate molecularTargetType P142668 FINISHED
Object receptor tyrosine kinase 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: receptor tyrosine kinase | Statement: [LOXO-195, molecularTargetType, receptor tyrosine kinase]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: molecularTargetType
Context triple: [LOXO-195, molecularTargetType, receptor tyrosine kinase]
  • A. hasMolecularTarget
    Indicates that one entity (such as a drug or compound) is directed toward, binds to, or specifically interacts with a particular molecular target (such as a protein, receptor, or gene).
  • B. isTherapeuticTargetIn
    Indicates that a biological entity (e.g., gene, protein, pathway) is used or proposed as a therapeutic target within a specified disease, condition, or treatment context.
  • C. regulatoryTarget
    Indicates that one entity is subject to control, influence, or governance by another entity under a regulatory or rule-based framework.
  • D. targetsReceptor chosen
    Indicates that one entity is directed toward, binds to, or is designed to act upon a specific receptor.
  • E. ligandType
    Indicates the specific kind or category of ligand associated with, or acting upon, an entity in the relationship.
  • 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_69e2458185f88190b0045227ee420411 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17cd9b3c0819096050f43a829ec0d completed April 29, 2026, 3:36 a.m.
PD Predicate disambiguation batch_69eed2c32e8c8190b73bb9965ed47d64 completed April 27, 2026, 3:06 a.m.
Created at: April 17, 2026, 3:30 p.m.