Triple
T11074314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ERBB2 |
E261825
|
entity |
| Predicate | genomicAlteration |
P97055
|
FINISHED |
| Object | gene amplification |
—
|
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: gene amplification | Statement: [ERBB2, genomicAlteration, gene amplification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genomicAlteration Context triple: [ERBB2, genomicAlteration, gene amplification]
-
A.
genomeCharacteristic
Indicates that an entity has a specific property, feature, or attribute related to its genome.
-
B.
geneticElement
Indicates that one entity is a genetic element (such as a gene, sequence, or structural unit of genetic material) associated with or characterized by the other entity.
-
C.
genomeSequenced
Indicates that the complete DNA sequence of an organism’s genome has been determined and recorded.
-
D.
alternativeSplicingFeature
Indicates that a genomic region or element participates in an alternative splicing event, distinguishing it as a feature involved in generating splice variants.
-
E.
hasPharmacogenomicAssociation
Indicates that there is a documented relationship between a genetic variant and a drug’s response, efficacy, or toxicity.
- F. None of above. chosen
Provenance (4 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7994e32fc8190a6591d9e82b68f75 |
completed | April 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69d74415403c81909778bcd829e8832e |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.