Triple
T6065073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMN2 |
E135135
|
entity |
| Predicate | sequenceDifferenceType |
P68443
|
FINISHED |
| Object | C>T transition in exon 7 |
—
|
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: C>T transition in exon 7 | Statement: [SMN2, sequenceDifferenceType, C>T transition in exon 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sequenceDifferenceType Context triple: [SMN2, sequenceDifferenceType, C>T transition in exon 7]
-
A.
differenceFromStates
Indicates that one state or condition is distinct from, or deviates in some way from, another state or condition.
-
B.
differIn
Indicates that two entities are not the same in at least one specified aspect, attribute, or value.
-
C.
comparisonType
Indicates the specific kind of comparison being made between two or more values or entities (e.g., equality, inequality, ordering, or similarity).
-
D.
hasLexicalDifferencesWith
Indicates that two linguistic items differ from each other in their word choice or lexical form.
-
E.
sequencerType
Indicates the specific kind or category of sequencer associated with or used in relation to an entity.
- 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_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. |
| PDg | Predicate description generation | batch_69c04e8d4a148190bd8f95caae978e1b |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:10 p.m.