Triple
T22690271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CDK4 |
E561032
|
entity |
| Predicate | hasEnsemblGeneID |
P68677
|
FINISHED |
| Object | ENSG00000135446 |
—
|
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: ENSG00000135446 | Statement: [CDK4, hasEnsemblGeneID, ENSG00000135446]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnsemblGeneID Context triple: [CDK4, hasEnsemblGeneID, ENSG00000135446]
-
A.
EnsemblGeneID
chosen
Indicates a relationship that assigns or associates a biological entity (such as a gene) with its unique Ensembl gene identifier.
-
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
Indicates a relationship that assigns or links an entity to its unique gene identifier as defined in the NCBI Gene database.
-
D.
hasGene
Indicates that an entity possesses or contains a specific gene as part of its genetic makeup.
-
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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789a1fd08190bce5fa0babe695d3 |
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.