Triple
T25150358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Postscript: Contempt as a Virus |
E630057
|
entity |
| Predicate | comparesContemptTo |
P278
|
FINISHED |
| Object | infection |
—
|
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: infection | Statement: [Postscript: Contempt as a Virus, comparesContemptTo, infection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparesContemptTo Context triple: [Postscript: Contempt as a Virus, comparesContemptTo, infection]
-
A.
isEmbittered
Indicates that an entity harbors persistent bitterness or resentment, typically as a result of past experiences or perceived wrongs.
-
B.
opposedQualityTo
Indicates that one quality stands in direct opposition or contrast to another quality.
-
C.
hasOppositionalPerception
Indicates that one entity perceives another entity, concept, or situation as being in opposition, conflict, or contradiction to itself or its interests.
-
D.
isComparedTo
chosen
Indicates that one entity is evaluated or measured in relation to another to highlight similarities, differences, or relative qualities.
-
E.
comparisonLevel
Indicates the degree or intensity to which two or more entities are being compared within a given context.
- 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_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. |
Created at: April 18, 2026, 6:30 a.m.