Triple
T35664893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angelman syndrome |
E1030536
|
entity |
| Predicate | associatedChromosomeRegion |
P68690
|
FINISHED |
| Object | 15q11-q13 |
—
|
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: 15q11-q13 | Statement: [Angelman syndrome, associatedChromosomeRegion, 15q11-q13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedChromosomeRegion Context triple: [Angelman syndrome, associatedChromosomeRegion, 15q11-q13]
-
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.
affectsChromosome
Indicates a relationship where one entity produces a change or impact on the structure, function, or integrity of a chromosome.
-
D.
hasRegulatoryRegion
Indicates that one biological entity possesses or is associated with a specific regulatory DNA or genomic region that controls its expression or activity.
-
E.
locatedOnChromosomeArm
Indicates that one genetic element is situated on a specific arm (p or q) of a chromosome.
- 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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.