Triple
T19992686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APOE ε3 allele |
E494101
|
entity |
| Predicate | associatedWithLongevityRelativeToAPOE ε4 |
P138252
|
FINISHED |
| Object | more favorable |
—
|
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: more favorable | Statement: [APOE ε3 allele, associatedWithLongevityRelativeToAPOE ε4, more favorable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithLongevityRelativeToAPOE ε4 Context triple: [APOE ε3 allele, associatedWithLongevityRelativeToAPOE ε4, more favorable]
-
A.
oxidativeAging
Indicates a process where a substance or material undergoes deterioration or change over time due to reactions with oxygen or oxidative agents.
-
B.
geneticAffinity
Indicates a relationship where entities share a notable degree of genetic similarity or relatedness.
-
C.
positionOnAging
Indicates a stance, opinion, or policy that an entity holds regarding aging or age-related issues.
-
D.
lifespan
Indicates the duration of time between an entity’s birth (or creation) and its death (or end).
-
E.
geneticInfluence
Indicates that one entity affects or contributes to the genetic traits, characteristics, or heredity of another entity.
- 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.