Triple
T6065074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMN2 |
E135135
|
entity |
| Predicate | sequenceDifferenceConsequence |
P68444
|
FINISHED |
| Object | disrupted exonic splicing enhancer |
—
|
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: disrupted exonic splicing enhancer | Statement: [SMN2, sequenceDifferenceConsequence, disrupted exonic splicing enhancer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sequenceDifferenceConsequence Context triple: [SMN2, sequenceDifferenceConsequence, disrupted exonic splicing enhancer]
-
A.
hasConsequence
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
B.
narrativeConsequence
Indicates that one event, action, or state occurs as a direct result or outcome of another within a narrative sequence.
-
C.
announcedConsequence
Indicates that one entity has publicly stated or declared a specific outcome or consequence that will result from an action, event, or condition.
-
D.
adaptationDifference
Indicates a difference or change in how two entities adapt or have adapted relative to each other.
-
E.
differIn
Indicates that two entities are not the same in at least one specified aspect, attribute, or value.
- 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.