Triple
T34091335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nav1.1 sodium channel |
E874308
|
entity |
| Predicate | mutationTypeAssociated |
P68674
|
FINISHED |
| Object | loss-of-function mutations |
—
|
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: loss-of-function mutations | Statement: [Nav1.1 sodium channel, mutationTypeAssociated, loss-of-function mutations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mutationTypeAssociated Context triple: [Nav1.1 sodium channel, mutationTypeAssociated, loss-of-function mutations]
-
A.
mutationType
chosen
Indicates the specific kind or category of genetic alteration that has occurred in an entity.
-
B.
mutationAssociatedWith
Indicates that a specific genetic mutation is linked or related to another entity, such as a disease, trait, or molecular effect.
-
C.
secondaryMutation
Indicates that an additional, subsequent genetic alteration has occurred following an initial mutation in the same biological context.
-
D.
alterationType
Indicates the specific kind or category of change or modification that has been applied to an entity or relationship.
-
E.
changeType
Indicates the specific kind or category of modification that has occurred to an entity or relationship.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70c16095081908ffa34ea55556a65 |
completed | May 3, 2026, 8:49 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:52 a.m.