Triple
T33389033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SARS-CoV-2 spike glycoprotein |
E854994
|
entity |
| Predicate | hasNotableMutation |
P203628
|
FINISHED |
| Object | D614G |
—
|
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: D614G | Statement: [SARS-CoV-2 spike glycoprotein, hasNotableMutation, D614G]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableMutation Context triple: [SARS-CoV-2 spike glycoprotein, hasNotableMutation, D614G]
-
A.
hasNotableDelta
Indicates that there is a significant or noteworthy change or difference between two compared entities or states.
-
B.
hasNotableOperation
Indicates that an entity is associated with a significant or noteworthy operation, activity, or procedure.
-
C.
hasHumanModification
Indicates that an entity has been altered, influenced, or modified as a result of human activity or intervention.
-
D.
hasNotableTransition
Indicates that an entity undergoes or is associated with a significant change, shift, or transformation in state, condition, or role.
-
E.
hasMutationSystem
Indicates that one entity possesses or employs a particular mutation system or mechanism for generating or managing mutations.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01b841f5508190832bba00cf795bad |
completed | May 11, 2026, 11:06 a.m. |
| PD | Predicate disambiguation | batch_6a01b59541fc8190a9b13a55327c4aa1 |
completed | May 11, 2026, 10:55 a.m. |
| PDg | Predicate description generation | batch_6a01b8412624819086cf63e1b1f7eff1 |
completed | May 11, 2026, 11:06 a.m. |
Created at: May 1, 2026, 1:35 a.m.