Triple
T22692340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMN1 |
E561082
|
entity |
| Predicate | relatedPathway |
P38196
|
FINISHED |
| Object | mRNA splicing via spliceosome |
—
|
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: mRNA splicing via spliceosome | Statement: [SMN1, relatedPathway, mRNA splicing via spliceosome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedPathway Context triple: [SMN1, relatedPathway, mRNA splicing via spliceosome]
-
A.
regulatoryPathway
Indicates that one entity is part of, or participates in, a biological or organizational regulatory pathway that controls the activity, expression, or behavior of another.
-
B.
hasPathway
Indicates that there exists a route, channel, or sequence of steps through which one entity leads, connects, or gives access to another.
-
C.
supportsPathway
chosen
Indicates that one entity contributes to, enables, or maintains the functioning or progression of a specified pathway.
-
D.
relatedPass
Indicates that one pass is associated with or connected to another pass in some relevant way.
-
E.
relatedIntermediate
Indicates an indirect or intermediate relationship between two entities, typically via one or more other entities or steps rather than a direct connection.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789ba0148190891781d05ec64f3c |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:13 p.m.