Triple
T32940567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amnoonviridae |
E842652
|
entity |
| Predicate | hasGenome |
P29824
|
FINISHED |
| Object | segmented negative-sense RNA genome |
—
|
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: segmented negative-sense RNA genome | Statement: [Amnoonviridae, hasGenome, segmented negative-sense RNA genome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenome Context triple: [Amnoonviridae, hasGenome, segmented negative-sense RNA genome]
-
A.
hasGenomeStructure
Indicates that one entity possesses or is characterized by a specific genome organization or arrangement.
-
B.
hasGenomeType
chosen
Indicates that an entity possesses or is characterized by a specific type or classification of genome.
-
C.
haveGenomeFeatures
Indicates that an entity possesses or is associated with specific genomic features (such as genes, regulatory elements, or sequence annotations).
-
D.
hasGene
Indicates that an entity possesses or contains a specific gene as part of its genetic makeup.
-
E.
genomeSequenced
Indicates that the complete DNA sequence of an organism’s genome has been determined and recorded.
- 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 1, 2026, 1:20 a.m.