Triple
T19992651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APOE ε3 allele |
E494101
|
entity |
| Predicate | hasAminoAcidAtPosition158 |
P68686
|
FINISHED |
| Object | arginine |
—
|
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: arginine | Statement: [APOE ε3 allele, hasAminoAcidAtPosition158, arginine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAminoAcidAtPosition158 Context triple: [APOE ε3 allele, hasAminoAcidAtPosition158, arginine]
-
A.
hasAminoAcidChange
Indicates that an entity (such as a protein or gene variant) involves or results in a specific change from one amino acid to another in its sequence.
-
B.
hasNitrogenousBase
Indicates that one entity possesses or is associated with a specific nitrogenous base as a component or characteristic.
-
C.
hasProteinFeature
chosen
Indicates that a protein possesses a specific structural or functional feature, such as a domain, motif, or modification site.
-
D.
hasEnzymeCommissionNumber
Indicates that an entity is associated with a specific Enzyme Commission (EC) number that classifies its enzymatic activity.
-
E.
hasAllele
Indicates that a biological entity possesses or carries a specific allele variant of a gene.
- 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_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. |
Created at: April 11, 2026, 3:31 p.m.