Triple
T10609994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dravet syndrome |
E275979
|
entity |
| Predicate | hasOMIMID |
P68676
|
FINISHED |
| Object | 607208 |
—
|
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: 607208 | Statement: [Dravet syndrome, hasOMIMID, 607208]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOMIMID Context triple: [Dravet syndrome, hasOMIMID, 607208]
-
A.
OMIMID
chosen
Indicates that an entity (typically a gene or disease) is associated with a specific OMIM (Online Mendelian Inheritance in Man) identifier in the OMIM database.
-
B.
hasGeneticLocus
Indicates that a genetic feature or trait is located at, or associated with, a specific position (locus) on a genome or chromosome.
-
C.
NCBIGeneID
Indicates a relationship that assigns or links an entity to its unique gene identifier as defined in the NCBI Gene database.
-
D.
hasPharmacogenomicAssociation
Indicates that there is a documented relationship between a genetic variant and a drug’s response, efficacy, or toxicity.
-
E.
hasTargetDisease
Indicates that an entity (such as a treatment, study, or intervention) is directed toward, intended to affect, or primarily concerned with a specified disease.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df59468881909b0c67d3f08c4b76 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7a223c8190854409d76368f3e8 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 7:32 p.m.