Triple
T33404146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayhem |
E855391
|
entity |
| Predicate | hasVirusElement |
P100533
|
FINISHED |
| Object | ID-7 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: ID-7 virus | Statement: [Mayhem, hasVirusElement, ID-7 virus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVirusElement Context triple: [Mayhem, hasVirusElement, ID-7 virus]
-
A.
hasForensicElement
Indicates that something includes, involves, or is characterized by a forensic component, aspect, or feature.
-
B.
hasViralOrigin
Indicates that something originates from, is caused by, or is derived from a virus.
-
C.
associatedWithVirusSpecies
Indicates a relationship where one entity is linked or connected to a particular virus species, typically through relevance, involvement, or attribution.
-
D.
virusInvolved
chosen
Indicates that a virus participates in, influences, or is causally involved in a specified process, event, or relationship.
-
E.
hasThreatType
Indicates that an entity is associated with, or characterized by, a specific type or category of threat.
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: May 1, 2026, 1:36 a.m.