Triple
T6065101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMN2 |
E135135
|
entity |
| Predicate | databaseCrossReference |
P33159
|
FINISHED |
| Object | HGNC:11103 |
—
|
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: HGNC:11103 | Statement: [SMN2, databaseCrossReference, HGNC:11103]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: databaseCrossReference Context triple: [SMN2, databaseCrossReference, HGNC:11103]
-
A.
hasOrthologsWith
Indicates that two genes or proteins in different species are orthologous, meaning they originated from a common ancestral gene and typically retain similar functions.
-
B.
citesAs
Indicates that one entity references or acknowledges another as a source of information, authority, or evidence.
-
C.
relatedIdentifier
chosen
Indicates that one identifier is associated with another identifier that refers to the same or a related entity in a different context or system.
-
D.
citationSystem
Indicates a relationship where one entity specifies or uses a particular system, style, or standard for formatting and managing citations.
-
E.
isCitedWithTaxonName
Indicates that a work, statement, or reference is cited together with a specific taxon name in a taxonomic or scientific context.
- 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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05723c91c819090b4d4672e72f9f3 |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049f031408190b08b2766237c5dd0 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:10 p.m.