Triple
T23466458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RefSeq |
E569113
|
entity |
| Predicate | hasIdentifierPrefix |
P46986
|
FINISHED |
| Object | NM_ (mRNA RefSeq accessions) |
—
|
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: NM_ (mRNA RefSeq accessions) | Statement: [RefSeq, hasIdentifierPrefix, NM_ (mRNA RefSeq accessions)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIdentifierPrefix Context triple: [RefSeq, hasIdentifierPrefix, NM_ (mRNA RefSeq accessions)]
-
A.
haveIdentifier
chosen
Indicates that an entity is associated with a specific identifier used to uniquely reference or distinguish it.
-
B.
hasPrefix
Indicates that one entity occurs at the beginning of another entity, serving as its starting segment or initial substring.
-
C.
hasCatalogNumberPrefix
Indicates that an item’s catalog number begins with a specified prefix.
-
D.
hasRouteIdentifier
Indicates that an entity is associated with a specific route code or identifier used to distinguish it from other routes.
-
E.
hasIdentifierSystem
Indicates that an entity is associated with a particular system or scheme used to assign and manage its identifiers.
- 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a6faaf8c8190b4fd191c54e1acea |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:54 p.m.