Triple
T31535842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | An Essay on the Shaking Palsy |
E804597
|
entity |
| Predicate | originalTermUsedForDisease |
P46176
|
FINISHED |
| Object | shaking palsy |
—
|
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: shaking palsy | Statement: [An Essay on the Shaking Palsy, originalTermUsedForDisease, shaking palsy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalTermUsedForDisease Context triple: [An Essay on the Shaking Palsy, originalTermUsedForDisease, shaking palsy]
-
A.
diseaseUsed
Indicates that a particular disease is employed or utilized as a tool, model, or condition within a given context or process.
-
B.
termAlsoUsedFor
chosen
Indicates that one term is also used to refer to the same or closely related concept as another term.
-
C.
usedTerm
Indicates that one entity employed, referenced, or applied a particular term in some context.
-
D.
diseaseName
Indicates that the associated value specifies the name or designation of a particular disease.
-
E.
hasEponymousDisease
Indicates that an entity (typically a person) has a disease named after them.
- 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_6a00d6aff0a08190a330dd0c7c1352f9 |
completed | May 10, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_6a00d60f2a508190aeaf5a9d8af9c39e |
completed | May 10, 2026, 7:01 p.m. |
Created at: April 30, 2026, 10:03 p.m.