Triple
T8416688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Two Minutes Hate |
E198744
|
entity |
| Predicate | manipulationMethod |
P43307
|
FINISHED |
| Object | scapegoating |
—
|
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: scapegoating | Statement: [Two Minutes Hate, manipulationMethod, scapegoating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: manipulationMethod Context triple: [Two Minutes Hate, manipulationMethod, scapegoating]
-
A.
manipulatedBy
Indicates that an entity is controlled, influenced, or operated by another entity, often in a deliberate or strategic manner.
-
B.
controlMethods
chosen
Indicates the methods or techniques used by one entity to direct, regulate, or influence the behavior, operation, or state of another entity.
-
C.
mobilizationMethod
Indicates the method or process by which resources, people, or assets are organized and activated for a particular purpose or operation.
-
D.
interactionMechanism
Indicates the process or means by which one entity affects, influences, or interacts with another.
-
E.
method
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb84c5121081908efa3eca25406d3a |
completed | March 31, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:06 p.m.