Triple

T19992659
Position Surface form Disambiguated ID Type / Status
Subject APOE ε3 allele E494101 entity
Predicate consideredRiskStatusForAlzheimersDisease P138246 FINISHED
Object average risk 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: average risk | Statement: [APOE ε3 allele, consideredRiskStatusForAlzheimersDisease, average risk]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: consideredRiskStatusForAlzheimersDisease
Context triple: [APOE ε3 allele, consideredRiskStatusForAlzheimersDisease, average risk]
  • A. hasRiskFrom
    Indicates that one entity is exposed to or may suffer potential harm, loss, or adverse effects as a result of another entity.
  • B. riskFactorForDeath
    Indicates that something increases the likelihood or probability of death occurring.
  • C. requiresAssessmentOf
    Indicates that one entity necessitates an evaluation, review, or judgment to be performed on another entity before proceeding or fulfilling a condition.
  • D. riskAssessmentBy
    Indicates that a risk assessment is performed, evaluated, or provided by a specific agent or entity.
  • E. diagnosedWith
    Indicates that a subject has been identified, typically by a medical professional, as having a particular disease or medical condition.
  • F. None of above. chosen

Provenance (4 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_69da626a67648190af9653832a3aeced completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e65fe10ffc81908c94168b0a8ea9c9 completed April 20, 2026, 5:18 p.m.
PD Predicate disambiguation batch_69e537fd311881908448f2aea8b4812e completed April 19, 2026, 8:15 p.m.
PDg Predicate description generation batch_69e543c42c688190a22f4d31ec692377 completed April 19, 2026, 9:06 p.m.
Created at: April 11, 2026, 3:31 p.m.