Triple
T31535174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | alpha-synuclein |
E804584
|
entity |
| Predicate | aggregationState |
P3520
|
FINISHED |
| Object | forms amyloid fibrils |
—
|
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: forms amyloid fibrils | Statement: [alpha-synuclein, aggregationState, forms amyloid fibrils]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aggregationState Context triple: [alpha-synuclein, aggregationState, forms amyloid fibrils]
-
A.
aggregateState
Indicates the overall or combined condition or status resulting from multiple underlying states or components.
-
B.
aggregationProperty
Indicates that one entity serves as an aggregation or summary of values or instances associated with another entity.
-
C.
stateOfCollection
Indicates the current condition, status, or configuration that a collection (of items, data, or entities) is in at a given point in time.
-
D.
supportsAggregation
Indicates that one entity enables or allows another entity to be combined, grouped, or summarized with others through an aggregation operation.
-
E.
associatedState
chosen
Indicates that one entity is linked or connected to a particular state, condition, or status of another entity.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8055f8081908f635fe04654b5fe |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:03 p.m.