Triple
T22693498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EWSR1 |
E561108
|
entity |
| Predicate | proteinDomain |
P149327
|
FINISHED |
| Object | N-terminal low-complexity prion-like domain |
—
|
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: N-terminal low-complexity prion-like domain | Statement: [EWSR1, proteinDomain, N-terminal low-complexity prion-like domain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proteinDomain Context triple: [EWSR1, proteinDomain, N-terminal low-complexity prion-like domain]
-
A.
uniprotId
Indicates that an entity is associated with a specific UniProt database identifier for a protein.
-
B.
proteinProduct
Indicates that one entity is the protein that is produced or encoded by another entity (such as a gene or transcript).
-
C.
typicalProtein
Indicates that one entity is a representative or characteristic example of a particular protein type or class.
-
D.
proteinContent
Indicates the amount or proportion of protein present in a given entity or substance.
-
E.
hasProteinBinding
Indicates that one entity is capable of physically binding to or interacting specifically with a protein.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789c6ae481908975b7d27e7624ac |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:13 p.m.