Triple
T36659910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CYP3A5 |
E905090
|
entity |
| Predicate | alleleCYP3A5*6 |
P78759
|
FINISHED |
| Object | non-functional 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-functional allele | Statement: [CYP3A5, alleleCYP3A5*6, non-functional allele]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alleleCYP3A5*6 Context triple: [CYP3A5, alleleCYP3A5*6, non-functional 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.
geneticStatus
Indicates the genetic condition or variant state an entity has in relation to a specific gene or set of genes.
- 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_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:11 p.m.