Triple
T8372292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huntington's chorea |
E197487
|
entity |
| Predicate | encodesMutantProtein |
P14248
|
FINISHED |
| Object | mutant huntingtin protein |
—
|
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: mutant huntingtin protein | Statement: [Huntington's chorea, encodesMutantProtein, mutant huntingtin protein]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encodesMutantProtein Context triple: [Huntington's chorea, encodesMutantProtein, mutant huntingtin protein]
-
A.
hasAminoAcidChange
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.
encodes
chosen
Indicates that one entity contains or represents the information, instructions, or structure of another in a coded or symbolic form.
-
C.
mutationAssociatedWith
Indicates that a specific genetic mutation is linked or related to another entity, such as a disease, trait, or molecular effect.
-
D.
mutationType
Indicates the specific kind or category of genetic alteration that has occurred in an entity.
-
E.
encodedIn
Indicates that one entity is represented, stored, or expressed within another entity using a specific encoding or format.
- 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_69ca82f56730819080cec5d991c76f4c |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80a6944081909c4547688c9e70ae |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cd04b08190ab5f72afd22a7967 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:01 p.m.