Triple
T8902173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | supplementary motor area |
E211954
|
entity |
| Predicate | lesionAssociatedWith |
P33872
|
FINISHED |
| Object | SMA syndrome |
—
|
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: SMA syndrome | Statement: [supplementary motor area, lesionAssociatedWith, SMA syndrome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lesionAssociatedWith Context triple: [supplementary motor area, lesionAssociatedWith, SMA syndrome]
-
A.
lesionAssociatedWithSymptom
chosen
Indicates that a particular lesion is linked to, or occurs together with, a specific symptom.
-
B.
hasAssociatedDisease
Indicates that an entity is linked to, or commonly occurs with, a particular disease or medical condition.
-
C.
affectsAnatomicalLocation
Indicates that one entity produces an effect on, or has an impact at, a specific anatomical location.
-
D.
dysfunctionAssociatedWith
Indicates a relationship where a dysfunction is linked or correlated with another condition, factor, or entity.
-
E.
notablyAssociatedWith
Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
- 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_69ca83918d3081909b326fa3750cb8c8 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc642a104081908df2d64e8f9ad0c8 |
completed | April 1, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:55 p.m.