Triple
T34091239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCN1A |
E874307
|
entity |
| Predicate | RefSeq_mRNA |
P178216
|
FINISHED |
| Object | NM_001165963 |
—
|
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: NM_001165963 | Statement: [SCN1A, RefSeq_mRNA, NM_001165963]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RefSeq_mRNA Context triple: [SCN1A, RefSeq_mRNA, NM_001165963]
-
A.
primaryTranscript
Indicates that one entity is the initial RNA transcript directly produced from the transcription of another entity’s DNA sequence, prior to any RNA processing.
-
B.
EnsemblGeneID
Indicates a relationship that assigns or associates a biological entity (such as a gene) with its unique Ensembl gene identifier.
-
C.
ribosomalRNAFeatures
Indicates features or characteristics specifically associated with ribosomal RNA, such as its structural, functional, or sequence-related properties.
-
D.
NCBIGeneID
Indicates a relationship that assigns or links an entity to its unique gene identifier as defined in the NCBI Gene database.
-
E.
encodedByGene
Indicates that a particular gene is responsible for producing or specifying the sequence of a given molecule (such as a protein or RNA).
- F. None of above. chosen
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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70c53062c8190b4cb7be22ab00bc7 |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:52 a.m.