Triple
T22692767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5q13 (SMN1) |
E561092
|
entity |
| Predicate | chromosomeStrand |
P42088
|
FINISHED |
| Object | plus strand (forward) |
—
|
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: plus strand (forward) | Statement: [5q13 (SMN1), chromosomeStrand, plus strand (forward)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chromosomeStrand Context triple: [5q13 (SMN1), chromosomeStrand, plus strand (forward)]
-
A.
hasStrand
chosen
Indicates that one entity possesses or is associated with a particular strand or orientation relative to another entity.
-
B.
locatedOnChromosomeArm
Indicates that one genetic element is situated on a specific arm (p or q) of a chromosome.
-
C.
originalChannelStrand
Indicates that one entity is the original strand or source channel from which another channel or strand is derived or referenced.
-
D.
locatedOnChromosome
Indicates that a gene or genetic element is situated on a specific chromosome.
-
E.
chromosomalLocation
Indicates the specific position or region on a chromosome where a genetic element (such as a gene or marker) 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789ba0148190891781d05ec64f3c |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:13 p.m.