Triple
T25150357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Postscript: Contempt as a Virus |
E630057
|
entity |
| Predicate | describesContemptAs |
P158781
|
FINISHED |
| Object | 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: virus | Statement: [Postscript: Contempt as a Virus, describesContemptAs, virus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesContemptAs Context triple: [Postscript: Contempt as a Virus, describesContemptAs, virus]
-
A.
derogatesFrom
Indicates that one entity diminishes, belittles, or detracts from the value, reputation, or importance of another entity.
-
B.
describesAggressionAs
Indicates how one entity characterizes or portrays the aggression exhibited by another entity.
-
C.
disrespect
Indicates a relationship in which one entity shows a lack of respect, regard, or consideration toward another.
-
D.
correctsAberration
Indicates that one entity counteracts, fixes, or compensates for an error, flaw, or deviation present in another entity.
-
E.
insultedAs
Indicates that one entity directed an insulting or offensive remark or action toward another entity, characterizing the target in a demeaning way.
- 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 18, 2026, 6:30 a.m.