Triple
T10291893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BCRP |
E241383
|
entity |
| Predicate | effectOfPolymorphism |
P68586
|
FINISHED |
| Object | altered transporter expression |
—
|
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: altered transporter expression | Statement: [BCRP, effectOfPolymorphism, altered transporter expression]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOfPolymorphism Context triple: [BCRP, effectOfPolymorphism, altered transporter expression]
-
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.
geneticInfluence
Indicates that one entity affects or contributes to the genetic traits, characteristics, or heredity of another entity.
-
D.
affectsVariant
Indicates that one entity has an influence or impact on a specific variant or version of another entity.
-
E.
predictedEffect
chosen
Indicates that one entity is expected to cause, influence, or result in a particular outcome or consequence for another entity.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f117708190928f92ae2611d724 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:42 a.m.