Triple
T34187367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GNAI3 |
E876997
|
entity |
| Predicate | hasGeneID |
P68678
|
FINISHED |
| Object | NCBI Gene:2773 |
—
|
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: NCBI Gene:2773 | Statement: [GNAI3, hasGeneID, NCBI Gene:2773]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeneID Context triple: [GNAI3, hasGeneID, NCBI Gene:2773]
-
A.
hasGene
Indicates that an entity possesses or contains a specific gene as part of its genetic makeup.
-
B.
hasHGNCID
Indicates that an entity (typically a gene) is associated with a specific identifier assigned by the HUGO Gene Nomenclature Committee (HGNC).
-
C.
NCBIGeneID
chosen
Indicates a relationship that assigns or links an entity to its unique gene identifier as defined in the NCBI Gene database.
-
D.
EnsemblGeneID
Indicates a relationship that assigns or associates a biological entity (such as a gene) with its unique Ensembl gene identifier.
-
E.
hasGeneticLocus
Indicates that a genetic feature or trait is located at, or associated with, a specific position (locus) on a genome or 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_69f349ae640c8190b9cd220b5368d8b6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 1, 2026, 1:55 a.m.