Triple
T6003487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alimta |
E133650
|
entity |
| Predicate | targetsEnzyme |
P37016
|
FINISHED |
| Object | thymidylate synthase |
—
|
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: thymidylate synthase | Statement: [Alimta, targetsEnzyme, thymidylate synthase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsEnzyme Context triple: [Alimta, targetsEnzyme, thymidylate synthase]
-
A.
enzymeType
Indicates the specific class or category of enzyme associated with an entity or reaction.
-
B.
targetsGene
Indicates that one entity is directed toward, acts upon, or is intended to affect a specific gene.
-
C.
regulatoryTarget
Indicates that one entity is subject to control, influence, or governance by another entity under a regulatory or rule-based framework.
-
D.
targetOrganism
Indicates that an action, process, or effect is directed toward or intended to impact a particular organism.
-
E.
hasMolecularTarget
chosen
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).
- 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f0f63148190826198281dce3713 |
completed | March 22, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c049e3316c819087ea635fa7ee8472 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.