Triple
T22871276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CYP2C9 |
E567200
|
entity |
| Predicate | polymorphismsAffect |
P92924
|
FINISHED |
| Object | enzyme activity |
—
|
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: enzyme activity | Statement: [CYP2C9, polymorphismsAffect, enzyme activity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: polymorphismsAffect Context triple: [CYP2C9, polymorphismsAffect, enzyme activity]
-
A.
protectiveAlleleForDisease
Indicates that the presence of a specific allele reduces the risk, severity, or likelihood of developing a particular disease.
-
B.
affectsVariant
Indicates that one entity has an influence or impact on a specific variant or version of another entity.
-
C.
geneticInfluence
Indicates that one entity affects or contributes to the genetic traits, characteristics, or heredity of another entity.
-
D.
hasPharmacogenomicAssociation
chosen
Indicates that there is a documented relationship between a genetic variant and a drug’s response, efficacy, or toxicity.
-
E.
riskAlleleForDisease
Indicates that a specific allele is associated with an increased risk of developing a particular disease.
- 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f05c688819097ba3d24ea8e52f5 |
completed | April 29, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69eed2d8c0608190afef4c4e530c0e2c |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:38 p.m.