Triple
T22863026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LOXO-305 |
E566975
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | LOXO 305 |
—
|
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: LOXO 305 | Statement: [LOXO-305, hasAlternativeName, LOXO 305]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LOXO 305 Context triple: [LOXO-305, hasAlternativeName, LOXO 305]
-
A.
LOXO-305
chosen
LOXO-305 is a highly selective, non-covalent Bruton’s tyrosine kinase (BTK) inhibitor being developed as a targeted therapy for B-cell malignancies such as chronic lymphocytic leukemia.
-
B.
LOXO-195
LOXO-195 is a next-generation, highly selective TRK inhibitor developed to treat cancers that have developed resistance to earlier TRK-targeted therapies.
-
C.
LOXO-292
LOXO-292, also known as selpercatinib, is a targeted cancer therapy that selectively inhibits RET kinase and is used to treat certain RET-altered thyroid and lung cancers.
-
D.
LOXO
LOXO was the stock ticker symbol for Loxo Oncology, a biopharmaceutical company focused on developing targeted cancer therapies before its acquisition.
-
E.
Talycopa
Talycopa is a locality or area within the community of Llansamlet in Swansea, Wales.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17efdc3b08190be03d856aa86b277 |
completed | April 29, 2026, 3:46 a.m. |
Created at: April 17, 2026, 3:38 p.m.