Triple
T6065099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMN2 |
E135135
|
entity |
| Predicate | genomicContext |
P31422
|
FINISHED |
| Object | SMN locus at 5q13 with SMN1 and SMN2 in tandem repeat region |
—
|
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: SMN locus at 5q13 with SMN1 and SMN2 in tandem repeat region | Statement: [SMN2, genomicContext, SMN locus at 5q13 with SMN1 and SMN2 in tandem repeat region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genomicContext Context triple: [SMN2, genomicContext, SMN locus at 5q13 with SMN1 and SMN2 in tandem repeat region]
-
A.
genomeCharacteristic
Indicates that an entity has a specific property, feature, or attribute related to its genome.
-
B.
genomeSource
Indicates the origin or provenance of a genome, specifying where or how the genomic data was obtained.
-
C.
genomeSequenced
Indicates that the complete DNA sequence of an organism’s genome has been determined and recorded.
-
D.
genomeSize
Indicates the total amount of genetic material (e.g., in base pairs) contained in an organism’s genome.
-
E.
geneticMaterialOrganization
chosen
Indicates how genetic material is structured, arranged, or organized within or among biological entities.
- 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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05723c91c819090b4d4672e72f9f3 |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049f031408190b08b2766237c5dd0 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:10 p.m.