Triple
T32526222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superflu |
E831321
|
entity |
| Predicate | mutationRate |
P174548
|
FINISHED |
| Object | rapidly mutating |
—
|
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: rapidly mutating | Statement: [Superflu, mutationRate, rapidly mutating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mutationRate Context triple: [Superflu, mutationRate, rapidly mutating]
-
A.
mutationType
Indicates the specific kind or category of genetic alteration that has occurred in an entity.
-
B.
reproductionRate
Indicates the frequency or speed at which an entity produces new offspring or copies of itself over a given time or condition.
-
C.
rewardRate
Indicates the rate or level of compensation, benefit, or return provided in exchange for a particular action, contribution, or condition.
-
D.
mutationAssociatedWith
Indicates that a specific genetic mutation is linked or related to another entity, such as a disease, trait, or molecular effect.
-
E.
secondaryMutation
Indicates that an additional, subsequent genetic alteration has occurred following an initial mutation in the same biological context.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c518439c81908002caf84440dd8a |
completed | May 3, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 1:01 a.m.