Triple
T9524728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | substantia nigra |
E229730
|
entity |
| Predicate | degenerationLeadsTo |
P56495
|
FINISHED |
| Object | bradykinesia |
—
|
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: bradykinesia | Statement: [substantia nigra, degenerationLeadsTo, bradykinesia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: degenerationLeadsTo Context triple: [substantia nigra, degenerationLeadsTo, bradykinesia]
-
A.
degradationMechanism
Indicates the process or mechanism by which something deteriorates, breaks down, or loses its original quality or function over time.
-
B.
reasonForFurtherDeterioration
chosen
Indicates that one condition, event, or factor is identified as the cause of additional worsening or decline in another condition or situation.
-
C.
canDegenerateOn
Indicates that one entity has the potential to deteriorate, transform, or simplify into another entity under certain conditions.
-
D.
movementDecline
Indicates a reduction or worsening in the extent, frequency, or effectiveness of movement or mobility over time.
-
E.
breakdownLedTo
Indicates that one event or situation of breakdown caused or directly resulted in another event or outcome.
- 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_69ca847870a881909d8d751a7d29da39 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9899f99481908d374528716027f8 |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca56a3d088190bdc16670678fb6c6 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:59 p.m.