Triple
T34046643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Restless legs syndrome |
E873102
|
entity |
| Predicate | hasCoreSymptom |
P122518
|
FINISHED |
| Object | urge to move the legs |
—
|
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: urge to move the legs | Statement: [Restless legs syndrome, hasCoreSymptom, urge to move the legs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreSymptom Context triple: [Restless legs syndrome, hasCoreSymptom, urge to move the legs]
-
A.
hasPossibleSymptom
Indicates that an entity (such as a condition or disease) may be associated with a particular symptom that can potentially occur.
-
B.
isUsedForSymptom
Indicates that something (such as a treatment, medication, or intervention) is employed to address, alleviate, or manage a particular symptom.
-
C.
hasClinicalFeature
Indicates that an entity (such as a disease, condition, or case) exhibits or is characterized by a particular clinical sign, symptom, or feature.
-
D.
primarySymptom
chosen
Indicates that the related symptom is the main or most characteristic symptom associated with a condition, disease, or disorder.
-
E.
hasHealthConcern
Indicates that an entity has a specific health-related issue, condition, or concern associated with it.
- 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:51 a.m.