Triple
T22693283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HGNC:28350 |
E561104
|
entity |
| Predicate | linkedToPhenotype |
P133002
|
FINISHED |
| Object | motor neuron degeneration |
—
|
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: motor neuron degeneration | Statement: [HGNC:28350, linkedToPhenotype, motor neuron degeneration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToPhenotype Context triple: [HGNC:28350, linkedToPhenotype, motor neuron degeneration]
-
A.
associatedWithPhenotype
chosen
Indicates that an entity has a documented connection or correlation with a particular phenotype or observable trait.
-
B.
geneticallyLinkedTo
Indicates a relationship where two entities share a genetic connection, such as common ancestry, shared genes, or hereditary association.
-
C.
hasPharmacogenomicAssociation
Indicates that there is a documented relationship between a genetic variant and a drug’s response, efficacy, or toxicity.
-
D.
hasGeneticLocus
Indicates that a genetic feature or trait is located at, or associated with, a specific position (locus) on a genome or chromosome.
-
E.
geneticAffinity
Indicates a relationship where entities share a notable degree of genetic similarity or relatedness.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789c6ae481908975b7d27e7624ac |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:13 p.m.