Triple
T31535253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | locus coeruleus |
E804585
|
entity |
| Predicate | degeneratesIn |
P171935
|
FINISHED |
| Object | Parkinson's disease |
—
|
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: Parkinson's disease | Statement: [locus coeruleus, degeneratesIn, Parkinson's disease]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: degeneratesIn Context triple: [locus coeruleus, degeneratesIn, Parkinson's disease]
-
A.
canDegenerateOn
Indicates that one entity has the potential to deteriorate, transform, or simplify into another entity under certain conditions.
-
B.
decomposesIn
Indicates that one entity breaks down or separates into another entity or set of entities as its components or products.
-
C.
deconstructs
Indicates that one entity systematically takes apart, analyzes, or dismantles another entity or its structure into constituent elements.
-
D.
declineIn
Indicates a relationship where one entity experiences a decrease or reduction in the level, amount, or intensity of another entity over time.
-
E.
derogatesFrom
Indicates that one entity diminishes, belittles, or detracts from the value, reputation, or importance of another entity.
- 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.