Triple
T19992649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APOE ε3 allele |
E494101
|
entity |
| Predicate | locatedOnChromosomeRegion |
P68690
|
FINISHED |
| Object | 19q13.32 |
—
|
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: 19q13.32 | Statement: [APOE ε3 allele, locatedOnChromosomeRegion, 19q13.32]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnChromosomeRegion Context triple: [APOE ε3 allele, locatedOnChromosomeRegion, 19q13.32]
-
A.
locatedOnChromosome
Indicates that a gene or genetic element is situated on a specific chromosome.
-
B.
chromosomalLocation
chosen
Indicates the specific position or region on a chromosome where a genetic element (such as a gene or marker) is located.
-
C.
locatedOnChromosomeArm
Indicates that one genetic element is situated on a specific arm (p or q) of a chromosome.
-
D.
chromosomalLocationOfGene
Indicates the specific chromosomal position or region where a given gene is located.
-
E.
chromosomalBand
Indicates a relationship where a specific chromosomal band (a defined region on a chromosome) is associated with or assigned to a chromosome or genomic feature.
- 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.