Triple

T1169499
Position Surface form Disambiguated ID Type / Status
Subject spinal muscular atrophy E24880 entity
Predicate hasRiskFactor P8576 FINISHED
Object family history of spinal muscular atrophy 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: family history of spinal muscular atrophy | Statement: [spinal muscular atrophy, hasRiskFactor, family history of spinal muscular atrophy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRiskFactor
Context triple: [spinal muscular atrophy, hasRiskFactor, family history of spinal muscular atrophy]
  • A. hasHealthConcern
    Indicates that an entity has a specific health-related issue, condition, or concern associated with it.
  • B. riskFeature chosen
    Indicates that one entity possesses or exhibits a characteristic, condition, or attribute that increases the likelihood or severity of a negative outcome for another entity or situation.
  • C. hasNotableHazard
    Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
  • D. hasHigh
    Indicates that an entity possesses a high level, degree, or intensity of a specified attribute or property.
  • E. mayBeComorbidWith
    Indicates that two conditions or disorders can occur together in the same individual, potentially influencing each other’s presence or severity.
  • 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_69a494082a7c819095004f423f294a64 completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bce821b481908bc278a3fa7973f4 completed March 1, 2026, 10:25 p.m.
PD Predicate disambiguation batch_69a4bb5656948190b0b1d5446ad06005 completed March 1, 2026, 10:19 p.m.
Created at: March 1, 2026, 7:45 p.m.