Triple
T28938903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTT |
E730391
|
entity |
| Predicate | mutationCauses |
P68687
|
FINISHED |
| Object | Huntington's disease |
E197487
|
NE 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: Huntington's disease | Statement: [HTT, mutationCauses, Huntington's disease]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mutationCauses Context triple: [HTT, mutationCauses, Huntington's disease]
-
A.
mutationAssociatedWith
chosen
Indicates that a specific genetic mutation is linked or related to another entity, such as a disease, trait, or molecular effect.
-
B.
secondaryMutation
Indicates that an additional, subsequent genetic alteration has occurred following an initial mutation in the same biological context.
-
C.
mutationType
Indicates the specific kind or category of genetic alteration that has occurred in an entity.
-
D.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
E.
migrationCause
Indicates the reason or driving factor that leads an entity to migrate from one place to another.
- F. None of above.
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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65b81d53881908f4e8f36867d2435 |
completed | May 2, 2026, 8:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a251f57cbf88190ad1f95cfa7fcca03 |
completed | June 7, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 8:34 a.m.