Triple
T23466547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BLAST |
E569115
|
entity |
| Predicate | blastnFor |
P152385
|
FINISHED |
| Object | nucleotide vs nucleotide |
—
|
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: nucleotide vs nucleotide | Statement: [BLAST, blastnFor, nucleotide vs nucleotide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blastnFor Context triple: [BLAST, blastnFor, nucleotide vs nucleotide]
-
A.
bindsNucleotide
Indicates that one entity physically attaches to or associates with a nucleotide molecule.
-
B.
bindsSequenceMotif
Indicates that one entity specifically recognizes and attaches to a particular sequence motif of another entity.
-
C.
EMBL-EBILocation
Indicates a relationship that specifies the physical or database location information as defined by the EMBL-EBI (European Molecular Biology Laboratory – European Bioinformatics Institute) standards.
-
D.
DNAAnalysis
Indicates that one entity performs or undergoes the examination and interpretation of DNA from another entity or source.
-
E.
genomeSource
Indicates the origin or provenance of a genome, specifying where or how the genomic data was obtained.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:54 p.m.