Triple
T19245326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INS gene |
E481234
|
entity |
| Predicate | locatedInChromosomalBand |
P68669
|
FINISHED |
| Object | 11p15.5 |
—
|
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: 11p15.5 | Statement: [INS gene, locatedInChromosomalBand, 11p15.5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInChromosomalBand Context triple: [INS gene, locatedInChromosomalBand, 11p15.5]
-
A.
locatedOnChromosome
Indicates that a gene or genetic element is situated on a specific chromosome.
-
B.
chromosomalLocation
Indicates the specific position or region on a chromosome where a genetic element (such as a gene or marker) is located.
-
C.
chromosomalBand
chosen
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.
-
D.
locatedOnChromosomeArm
Indicates that one genetic element is situated on a specific arm (p or q) of a chromosome.
-
E.
chromosomalLocationOfGene
Indicates the specific chromosomal position or region where a given gene is located.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb2c34e88190a338e5a7ba906425 |
completed | April 20, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:27 p.m.