Triple
T13959306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta variant |
E335749
|
entity |
| Predicate | hasProteinMutation |
P61676
|
FINISHED |
| Object | L452R |
—
|
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: L452R | Statement: [Delta variant, hasProteinMutation, L452R]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProteinMutation Context triple: [Delta variant, hasProteinMutation, L452R]
-
A.
hasAminoAcidChange
chosen
Indicates that an entity (such as a protein or gene variant) involves or results in a specific change from one amino acid to another in its sequence.
-
B.
hasProteinFeature
Indicates that a protein possesses a specific structural or functional feature, such as a domain, motif, or modification site.
-
C.
hasMutationCountInSpikeProtein
Indicates that an entity has a specified number of mutations located in its spike protein.
-
D.
hasProteinBinding
Indicates that one entity is capable of physically binding to or interacting specifically with a protein.
-
E.
hasPostTranslationalModification
Indicates that a biomolecule has undergone a specific chemical modification after its initial synthesis (translation), altering its structure or function.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e7b2f908190aa32f22298964746 |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:17 p.m.