Triple
T32940556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amnoonviridae |
E842652
|
entity |
| Predicate | isEnveloped |
P54329
|
FINISHED |
| Object | enveloped virus |
—
|
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: enveloped virus | Statement: [Amnoonviridae, isEnveloped, enveloped virus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEnveloped Context triple: [Amnoonviridae, isEnveloped, enveloped virus]
-
A.
enveloped
chosen
Indicates that one entity is completely or largely surrounded, covered, or enclosed by another.
-
B.
hasEnvoi
Indicates that one entity includes or is associated with an envoi, typically a concluding or dedicatory section appended to a main text or composition.
-
C.
engagementEnvelope
Indicates the spatial or contextual bounds within which an interaction, operation, or engagement between entities is valid or permitted.
-
D.
isTraditionallyWrappedWhen
Indicates that something is customarily enclosed or covered in another material or item during a particular time, event, or circumstance.
-
E.
encodedIn
Indicates that one entity is represented, stored, or expressed within another entity using a specific encoding or format.
- 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_69f6d110773c8190a1d22fdae038102f |
completed | May 3, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:20 a.m.