Triple
T36600221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CYP2B6 |
E902894
|
entity |
| Predicate | polymorphismIn |
P176460
|
FINISHED |
| Object | CYP2B6*6 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: CYP2B6*6 allele | Statement: [CYP2B6, polymorphismIn, CYP2B6*6 allele]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: polymorphismIn Context triple: [CYP2B6, polymorphismIn, CYP2B6*6 allele]
-
A.
polymorphic
Indicates that an entity can take on multiple distinct forms or types while maintaining a common interface or role in a relationship or action.
-
B.
workerPolymorphism
Indicates that an entity functions as a worker in multiple forms or roles, varying its behavior or type depending on context.
-
C.
polymorphismEffect
chosen
Indicates how a specific genetic polymorphism alters the effect, function, or outcome of a biological process, treatment, or phenotype.
-
D.
hasWorkerPolymorphism
Indicates that an entity supports multiple interchangeable worker implementations or roles that can perform the same task in different ways.
-
E.
typeOfInheritance
Indicates the kind or pattern of inheritance by which a trait, property, or characteristic is passed from one entity or generation to another.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.