Triple
T31535187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | alpha-synuclein |
E804584
|
entity |
| Predicate | toxicForm |
P171933
|
FINISHED |
| Object | soluble oligomers |
—
|
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: soluble oligomers | Statement: [alpha-synuclein, toxicForm, soluble oligomers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toxicForm Context triple: [alpha-synuclein, toxicForm, soluble oligomers]
-
A.
toxicTo
Indicates that one entity causes harm, poisoning, or adverse effects to another when exposed or applied.
-
B.
toxicPart
Indicates that one entity is a component or portion of another that is harmful, poisonous, or otherwise toxic.
-
C.
toxinType
Indicates the specific kind or category of toxin associated with an entity.
-
D.
toxicityRoute
Indicates the route or pathway through which a toxic effect or substance is delivered or exposed to an entity.
-
E.
toxicityType
Indicates the specific kind or category of toxic effect associated with a substance, action, or exposure.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:03 p.m.