Triple
T17262163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Filoviridae |
E419033
|
entity |
| Predicate | virionLength |
P126772
|
FINISHED |
| Object | up to about 1400 nm |
—
|
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: up to about 1400 nm | Statement: [Filoviridae, virionLength, up to about 1400 nm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: virionLength Context triple: [Filoviridae, virionLength, up to about 1400 nm]
-
A.
virionShape
Indicates the characteristic three-dimensional form or morphology of a virion.
-
B.
virusSubtype
Indicates the specific subtype classification of a virus within a broader virus type or strain.
-
C.
virusInvolved
Indicates that a virus participates in, influences, or is causally involved in a specified process, event, or relationship.
-
D.
associatedWithVirusSpecies
Indicates a relationship where one entity is linked or connected to a particular virus species, typically through relevance, involvement, or attribution.
-
E.
usesViralVector
Indicates that one entity employs a viral vector as a delivery mechanism or tool to introduce genetic material or components into another entity.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e717a348190ae6835fb08f38125 |
completed | April 19, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
| PDg | Predicate description generation | batch_69e39c2fedb881908bfed2c3e5f2616a |
completed | April 18, 2026, 2:58 p.m. |
Created at: April 10, 2026, 5:40 a.m.