Triple
T36659909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CYP3A5 |
E905090
|
entity |
| Predicate | alleleCYP3A5*3 |
P78759
|
FINISHED |
| Object | non-expressor allele |
—
|
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: non-expressor allele | Statement: [CYP3A5, alleleCYP3A5*3, non-expressor allele]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alleleCYP3A5*3 Context triple: [CYP3A5, alleleCYP3A5*3, non-expressor allele]
-
A.
hasPharmacogenomicAssociation
Indicates that there is a documented relationship between a genetic variant and a drug’s response, efficacy, or toxicity.
-
B.
hasAllele
chosen
Indicates that a biological entity possesses or carries a specific allele variant of a gene.
-
C.
riskAlleleForDisease
Indicates that a specific allele is associated with an increased risk of developing a particular disease.
-
D.
protectiveAlleleForDisease
Indicates that the presence of a specific allele reduces the risk, severity, or likelihood of developing a particular disease.
-
E.
O1Biotype
Indicates that an entity has or is classified by a specific biological type or category.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:11 p.m.