Triple
T31535854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | An Essay on the Shaking Palsy |
E804597
|
entity |
| Predicate | namedAfterAuthorIn |
P63
|
FINISHED |
| Object | Parkinson's disease |
—
|
NE NERFINISHED |
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: [An Essay on the Shaking Palsy, namedAfterAuthorIn, Parkinson's disease]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterAuthorIn Context triple: [An Essay on the Shaking Palsy, namedAfterAuthorIn, Parkinson's disease]
-
A.
namedAfter
chosen
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
B.
authorOrder
Indicates the sequence or ranking of authors associated with a work, specifying each author's position in the authorship list.
-
C.
hasAuthorSurname
Indicates that an entity (such as a work or publication) has an associated author whose family name is the specified surname.
-
D.
authorOfNamesFor
Indicates that one entity is the creator or originator of the names assigned to another entity or set of entities.
-
E.
hasAuthorGivenNames
Indicates that an entity is associated with the given (first and middle) name or names of its author.
- 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_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 30, 2026, 10:03 p.m.