Triple
T22863048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LOXO-305 |
E566975
|
entity |
| Predicate | clinicalDevelopmentPhase |
P114525
|
FINISHED |
| Object | clinical trials |
—
|
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: clinical trials | Statement: [LOXO-305, clinicalDevelopmentPhase, clinical trials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clinicalDevelopmentPhase Context triple: [LOXO-305, clinicalDevelopmentPhase, clinical trials]
-
A.
clinicalTrialPhase
Indicates the specific phase or stage of development a clinical trial is in within the overall clinical research process.
-
B.
studiesPhase
Indicates that an entity conducts research or examination on a particular phase or stage of a process, project, or phenomenon.
-
C.
developmentPhaseName
chosen
Indicates the specific stage or phase name within a broader development process or lifecycle.
-
D.
clinicalProgram
Indicates that an entity is part of, associated with, or classified under a specific clinical program or initiative.
-
E.
clinicalTesting
Indicates that an entity is involved in or associated with the process of systematically testing medical interventions, treatments, or procedures in a clinical setting.
- 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17efdc3b08190be03d856aa86b277 |
completed | April 29, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:38 p.m.